Use Application Signals wherever possible #149
Merged
+100
−88
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.
In this commit, we are changing
appsignals
,app_signals
,app_signals
, andapp signals
toapplicationsignals
,application_signals
,application-signals
, andapplication signals
wherever possible. Calloutaws-application-signals-team
was created here: https://github.com/orgs/aws-observability/teams/aws-application-signals-team and has correct permissions on this repo.Remaining usages:
aws_opentelemetry_configurator.py
- we have to support both old and new config names (e.g.OTEL_AWS_APP_SIGNALS_ENABLED
andOTEL_AWS_APPLICATION_SIGNALS_ENABLED
)application-signals-python-e2e-eks-test.yml
,application-signals-python-e2e-ec2-test.yml
,appsignals-python-e2e-eks-canary-test.yml
, andappsignals-python-e2e-ec2-canary-test.yml
- various reasons:appsignals
referenced in other repos that need to be updated first.appsignals
, which we have alarms on - changing is non-trivial.appsignals
- changing would break links (including runbooks).appsignals
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.