-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Add resource attributes to the OpAMP Extension's non-identifying attrs #37487
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
Comments
i can work on this. |
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
oh i can still do this... tbh forgot about it! oops! |
…pen-telemetry#38994) #### Description Introduces a new config struct element `IncludeResourceAttributes` which when enabled (default is false) copies the set resource attributes from the agent into the non-identifying attributes in the agent description message. #### Link to tracking issue Fixes open-telemetry#37487 #### Testing Unit #### Documentation n/a --------- Co-authored-by: Evan Bradley <[email protected]>
…pen-telemetry#38994) #### Description Introduces a new config struct element `IncludeResourceAttributes` which when enabled (default is false) copies the set resource attributes from the agent into the non-identifying attributes in the agent description message. #### Link to tracking issue Fixes open-telemetry#37487 #### Testing Unit #### Documentation n/a --------- Co-authored-by: Evan Bradley <[email protected]>
Component(s)
extension/opamp
Is your feature request related to a problem? Please describe.
I would love to have the resource attrs be available on the OpAMP messages which would help me understand the environment of the agent more effectively.
Describe the solution you'd like
It would be great if we had a way of copying over the resource attributes from the collector into the opamp extensions non-identifying attributes. I think we could do this by default into the non-identifying attrs without issue.
Describe alternatives you've considered
You could duplicate any of the resource attrs manually right now, but you have to do it one by one and explicitly which isn't scalable.
Additional context
No response
The text was updated successfully, but these errors were encountered: