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.

Sign up for GitHub

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

Jump to bottom

Support converting telemetry service from Otel config file #2949

Open
wildum opened this issue Mar 10, 2025 · 0 comments · May be fixed by #3038
Open

Support converting telemetry service from Otel config file #2949

wildum opened this issue Mar 10, 2025 · 0 comments · May be fixed by #3038
Assignees
@ptodev

Comments

@wildum
Copy link
Contributor

wildum commented Mar 10, 2025

The internal telemetry of the Otel collector can be configured (see https://opentelemetry.io/docs/collector/internal-telemetry/#activate-internal-telemetry-in-the-collector).

We should have a way to translate this into an Alloy-equivalent configuration.

We should maybe wait before starting on this because it might change a lot after 1.0
@wildum wildum changed the title Support converting telemetry config of Otel collector Support converting telemetry service from Otel config file Mar 10, 2025
@ptodev ptodev self-assigned this Mar 11, 2025
@ptodev ptodev linked a pull request Mar 19, 2025 that will close this issue
Add basic support for OTel's service/telemetry config argument #3038
Open
4 tasks
@ptodev ptodev linked a pull request Mar 19, 2025 that will close this issue
Open
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ptodev ptodev

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add basic support for OTel's service/telemetry config argument grafana/alloy
2 participants
@ptodev @wildum