Skip to content
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

[cmd/opampsupervisor] Add configurable telemetry options for supervisor #35582

Open
dpaasman00 opened this issue Oct 3, 2024 · 2 comments
Open
Labels

Comments

@dpaasman00
Copy link
Contributor

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. 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

Copy link
Contributor

github-actions bot commented Oct 3, 2024

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@evan-bradley evan-bradley removed the needs triage New item requiring triage label Oct 3, 2024
Copy link
Contributor

github-actions bot commented Dec 3, 2024

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.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants