-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrap TelemetrySettings providers to add component-identifying attributes #12384
base: main
Are you sure you want to change the base?
Changes from all commits
9238c22
8ef0c86
2fbd5b8
88e477d
806fb7a
9e0efa5
213ef9d
766266d
c242492
106dd59
57519e6
3d0711e
21e7841
90c88a5
15dc7dd
81be0d3
8124d82
fae6bb6
7f5ebd8
aa1f5e1
1ba12b6
5fe0643
17fdf81
5d7a01a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# Use this changelog template to create an entry for release notes. | ||
|
||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' | ||
change_type: 'enhancement' | ||
|
||
# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver) | ||
component: service | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: Internal metrics and spans now include component-related attributes. | ||
|
||
# One or more tracking issues or pull requests related to the change | ||
issues: [12217] | ||
|
||
# (Optional) One or more lines of additional information to render under the primary note. | ||
# These lines will be padded with 2 spaces and then inserted directly into the document. | ||
# Use pipe (|) for multiline entries. | ||
subtext: | | ||
All internal telemetry now includes one or more of the following metric/span attributes: | ||
- `otelcol.component.kind` | ||
- `otelcol.component.id` | ||
- `otelcol.pipeline.id` | ||
- `otelcol.signal` | ||
- `otelcol.signal.output` | ||
These attributes are defined in the [Pipeline Component Telemetry RFC](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/component-universal-telemetry.md#attributes), | ||
and identify the component instance from which the telemetry originates. | ||
These attribues are added automatically without changes to component code by wrapping the | ||
`MeterProvider` and `TracerProvider` provided to them. | ||
Components will be able to opt out of one or more of these attributes, but that API is not yet | ||
publicly available. | ||
|
||
# Optional: The change log or logs in which this entry should be included. | ||
# e.g. '[user]' or '[user, api]' | ||
# Include 'user' if the change is relevant to end users. | ||
# Include 'api' if there is a change to a library API. | ||
# Default: '[user]' | ||
change_logs: [user, api] | ||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This approach looks good to me. Thank you for putting this together. Are there any visible changes for end-users at this point?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say yes, since this adds
otelcol.component.id
and friends to basically all internal metrics/logs.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please add this to the subtext or create another user-facing changelog item?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The description of the item is "Internal metrics and spans now include component attributes", and the subtext already says "[The providers] automatically insert metric/span attributes which identify the originating component instance, as defined in the Pipeline Component Telemetry RFC". Do you think I should list the attributes explicitly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reworded the changelog and added more details, tell me whether you think it's sufficient.