Add SecretsManager and StepFunctions support. #203
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add SecretsManager and StepFunctions Support with the following change:
Add patch
_SecretsManagerExtension
and_StepFunctionsExtension
, extractSecretARN
,activityARN
andstateMachineArn
add into span attributes. The attributes will be retrieved from both request and response context.For
SecretARN
, it can be retrieved from two context paramters: 1).ARN
2).SecretId
:SecretId
can be secret name or secret arn, we only use it if it is an arn.Populate
RemoteResourceType
andRemoteResourceIdentifier
for SecretsManager and StepFunctions in ADOT python and update unit test and contract test to verify ADOT python performance.Contract test: for
test_stepfunctions_fault
, since it is not straightforward to trigger 500 CLientError directly, we register 500 events for the specific API call to simulate 500 scenario.Testing: E2E test performed to confirm trace, metrics and service maps are generated:
secret manager:
trace:
metrics:
step function:
trace:
metrics:
Service Map:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.