Skip to content

feat: Add Application Signals Dimensions to EMF exporter#1264

Merged
liustve merged 12 commits intomainfrom
appsignals-dimensions
Dec 12, 2025
Merged

feat: Add Application Signals Dimensions to EMF exporter#1264
liustve merged 12 commits intomainfrom
appsignals-dimensions

Conversation

@liustve
Copy link
Contributor

@liustve liustve commented Dec 10, 2025

Description of changes:

  • Added support for Application Signals dimensions (Service and Environment) in EMF exporters via the OTEL_METRICS_ADD_APPLICATION_SIGNALS_DIMENSIONS environment variable. When enabled, the exporters automatically add Service and Environment dimensions. Defaults to UnknownService and generic:default respectively based on resource attributes and cloud platform.

  • Application Signals dimensions are enabled by default when OTEL_METRICS_EXPORTER is set to awsemf. Users can opt out or disable this feature by explicitly setting OTEL_METRICS_ADD_APPLICATION_SIGNALS_DIMENSIONS to false.

  • chore: add Builder class for AwsEmf and Console exporters

image

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@liustve liustve requested a review from a team as a code owner December 10, 2025 01:44
wangzlei
wangzlei previously approved these changes Dec 11, 2025
liustve added a commit to aws-observability/aws-otel-python-instrumentation that referenced this pull request Dec 11, 2025
… exporter (#552)

*Description of changes:*
- Ports changes from:
aws-observability/aws-otel-java-instrumentation#1264

- Adds new `OTEL_METRICS_ADD_APPLICATION_SIGNALS_DIMENSIONS` environment
variable. When enabled, the exporters automatically add Service and
Environment dimensions. Defaults to `UnknownService` and
`generic:default` respectively based on resource attributes and cloud
platform.

- Application Signals dimensions are enabled by default when
OTEL_METRICS_EXPORTER is set to awsemf. Users can opt out or disable
this feature by explicitly setting
OTEL_METRICS_ADD_APPLICATION_SIGNALS_DIMENSIONS to false.

- Disable Application Signals Dimensions for Agent Observability path


By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.
@liustve liustve merged commit c4bc215 into main Dec 12, 2025
16 of 21 checks passed
@liustve liustve deleted the appsignals-dimensions branch December 12, 2025 05:31
yiyuan-he pushed a commit to yiyuan-he/aws-otel-python-instrumentation that referenced this pull request Dec 12, 2025
… exporter (aws-observability#552)

*Description of changes:*
- Ports changes from:
aws-observability/aws-otel-java-instrumentation#1264

- Adds new `OTEL_METRICS_ADD_APPLICATION_SIGNALS_DIMENSIONS` environment
variable. When enabled, the exporters automatically add Service and
Environment dimensions. Defaults to `UnknownService` and
`generic:default` respectively based on resource attributes and cloud
platform.

- Application Signals dimensions are enabled by default when
OTEL_METRICS_EXPORTER is set to awsemf. Users can opt out or disable
this feature by explicitly setting
OTEL_METRICS_ADD_APPLICATION_SIGNALS_DIMENSIONS to false.

- Disable Application Signals Dimensions for Agent Observability path


By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants