Custom emitter based on boto3 creates an infinite loop in the SDK about aws-xray-sdk-python HOT 3 OPEN

Hi @nsp-aws
I think your solution to exclude the GetRoleCredentials is correct in this case. From the SDK side itself, it may be difficult to identify all the possible AWS operations that may be called in a custom emitter. One solution that can possibly work is to let users provide a set of operations they want to ignore when botocore is patched. Similar to what has been done for the httplib patch.

Also, not sure how feasible it would be for you to use OpenTelemetry, but you can try writing your own SpanExporter (refer to the ConsoleSpanExporter) if that works for you.

from aws-xray-sdk-python.

Appreciate the response. Yes, having the ability to configure the operations that should be excluded would be adequate. OpenTelemetry is not being used on the current project so writing a custom exporter is not quite feasible. The core idea here was not have an external compute that would host either the collector or the X-RAY daemon. We needed to run the entire tracing system in-process.

Are you willing to accept a PR for configuring the operations for exclusion when patching boto?

from aws-xray-sdk-python.

Are you willing to accept a PR for configuring the operations for exclusion when patching boto?

Absolutely! I will be happy to review such a PR.

from aws-xray-sdk-python.