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
Is your feature request related to a problem? Please describe.
We would like to be able to associate extra user-specified information with the agent. In our case, we have a user that would like to be able to add extra identifying information (a separate unique ID) to OpAMP's agent description message.
The supervisor should support configuring extra agent_description attributes.
The configuration would end up looking like this:
agent:
description:
identifying_attributes:
key: valnon_identifying_attributes:
key: val
Where key and val are arbitrary key-value pairs.
These key-value pairs will be injected by the supervisor into the agent description retrieved during the bootstrap process. The values in the supervisor config will override the ones in the collector's agent description.
Describe alternatives you've considered
No response
Additional context
We discussed allowing the opamp extension to configure identifying attributes, but decided that it was susceptible to mis-configuration (identifying attributes must be on the agent's self-telemetry).
**Description:** <Describe what has changed.>
* Add options to the configuration that allows configuring the agent
description
**Link to tracking Issue:** Closes#32824
**Testing:** e2e test, unit tests for validation
**Documentation:**
* Updated spec with configuration parameters
---------
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
cparkins
pushed a commit
to AmadeusITGroup/opentelemetry-collector-contrib
that referenced
this issue
Jul 11, 2024
…metry#32819)
**Description:** <Describe what has changed.>
* Add options to the configuration that allows configuring the agent
description
**Link to tracking Issue:** Closesopen-telemetry#32824
**Testing:** e2e test, unit tests for validation
**Documentation:**
* Updated spec with configuration parameters
---------
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
Component(s)
cmd/opampsupervisor
Is your feature request related to a problem? Please describe.
We would like to be able to associate extra user-specified information with the agent. In our case, we have a user that would like to be able to add extra identifying information (a separate unique ID) to OpAMP's agent description message.
The spec allows for a user to specify necessary identifying attributes, as well as any non-identifying attributes a user would like to associate with the agent. See: https://github.com/open-telemetry/opamp-spec/blob/main/specification.md#agentdescriptionidentifying_attributes
Describe the solution you'd like
The supervisor should support configuring extra agent_description attributes.
The configuration would end up looking like this:
Where
key
andval
are arbitrary key-value pairs.These key-value pairs will be injected by the supervisor into the agent description retrieved during the bootstrap process. The values in the supervisor config will override the ones in the collector's agent description.
Describe alternatives you've considered
No response
Additional context
We discussed allowing the opamp extension to configure identifying attributes, but decided that it was susceptible to mis-configuration (identifying attributes must be on the agent's self-telemetry).
For more context, see:
#32644
The text was updated successfully, but these errors were encountered: