builtin:opentelemetry-metrics)Configure how OpenTelemetry metrics are ingested into Dynatrace via the OTLP endpoint.
Notes:
Changes made to these settings only apply to newly ingested data points. Data points that are already stored in Dynatrace will not change.
For OpenTelemetry trace/span settings, navigate to: Settings > Server-side service monitoring.
builtin:opentelemetry-metricsgroup:metricsenvironmentenvironment-default| GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:opentelemetry-metrics |
| SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:opentelemetry-metrics | |
| Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:opentelemetry-metrics |
To execute this request, you need an access token with Read settings (settings.read) scope. To learn how to obtain and use it, see Tokens and authentication.
meterNameToDimensionEnabledWhen enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs) and version will be added as dimensions (otel.scope.name and otel.scope.version) to ingested OTLP metrics.
Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually.
additionalAttributesToDimensionEnabledadditionalAttributesWhen enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
Notes:
Attributes must be added in their original format, as exported to Dynatrace by the telemetry source. For example, if the attribute is in PascalCase, the same case must be used when adding the attribute to the list.
Modifying this setting (renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually.
Dynatrace does not recommend changing/removing the attributes starting with "dt.". Dynatrace leverages these attributes to Enrich metrics.
toDropAttributesThe attributes defined in the list below will be dropped from all ingested OTLP metrics.
Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource).
Notes:
Attributes must be added in their original format, as exported to Dynatrace by the telemetry source. For example, if the attribute is in PascalCase, the same case must be used when adding the attribute to the list.
Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually.
Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
AdditionalAttributeItem objectenabledWhen enabled, the attribute will be added as a dimension to ingested metrics if present in the OpenTelemetry resource or in the instrumentation scope.
attributeKeyDropAttributeItem objectenabledWhen enabled, the attribute will be dropped on all ingested metrics.
attributeKey