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.
Currently monitoring the supervisor consists of capturing debug level logs from stdout. Soon there will be limited configurable logging options (see Additional Context) but there's no support for metrics or tracing or advanced logging options. As it matures, the supervisor should support more monitoring capabilities allowing any emitted telemetry to be captured.
Describe the solution you'd like
Something similar to the collector's service.telemetry configuration options could solve this problem. Granted it is not stable so there's room for change, but consistency between the collector and supervisor would be ideal. The service.telemetry config can be found here.
Describe alternatives you've considered
The supervisor could recognize the TelemetryConnectionSettings OpAMP message that is sent to the collector and send it's own telemetry to the specified destinations as well. However this would need more consideration to determine viability, especially since the supervisor currently doesn't forward this message to the collector for configuring collector telemetry.
Additional context
I have a PR open at the moment that lays the ground work for adding telemetry configuration starting with logs and the ability to specify log level and output. #35468
The text was updated successfully, but these errors were encountered:
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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Component(s)
cmd/opampsupervisor
Is your feature request related to a problem? Please describe.
Currently monitoring the supervisor consists of capturing debug level logs from stdout. Soon there will be limited configurable logging options (see Additional Context) but there's no support for metrics or tracing or advanced logging options. As it matures, the supervisor should support more monitoring capabilities allowing any emitted telemetry to be captured.
Describe the solution you'd like
Something similar to the collector's
service.telemetry
configuration options could solve this problem. Granted it is not stable so there's room for change, but consistency between the collector and supervisor would be ideal. Theservice.telemetry
config can be found here.Describe alternatives you've considered
The supervisor could recognize the
TelemetryConnectionSettings
OpAMP message that is sent to the collector and send it's own telemetry to the specified destinations as well. However this would need more consideration to determine viability, especially since the supervisor currently doesn't forward this message to the collector for configuring collector telemetry.Additional context
I have a PR open at the moment that lays the ground work for adding telemetry configuration starting with logs and the ability to specify log level and output. #35468
The text was updated successfully, but these errors were encountered: