You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Use this changelog template to create an entry for release notes.
2
+
3
+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4
+
change_type: enhancement
5
+
6
+
# The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
7
+
component: all
8
+
9
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10
+
note: Add support for resource detectors in service telemetry configuration
11
+
12
+
# One or more tracking issues or pull requests related to the change
13
+
issues: [14311, 10909]
14
+
15
+
# (Optional) One or more lines of additional information to render under the primary note.
16
+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17
+
# Use pipe (|) for multiline entries.
18
+
subtext: |
19
+
Service telemetry now supports automatic resource attribute detection using OpenTelemetry SDK detectors.
20
+
Configure detectors under `service.telemetry.detectors` to auto-detect environment variables, host information, and cloud metadata.
21
+
This aligns the Collector configuration surface with the declarative schema maintained in https://github.com/open-telemetry/opentelemetry-configuration (resource.yaml), while keeping extra SDK detectors available.
22
+
To use `OTEL_RESOURCE_ATTRIBUTES` and `OTEL_SERVICE_NAME` environment variables, enable the `env` detector.
0 commit comments