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

Module information should be available as part of otel factories initialization #6541

Open
ChrsMark opened this issue Jan 17, 2025 · 2 comments
Labels
opentelemetry Related to the Elastic Distribution of the OpenTelemetry Collector Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Comments

@ChrsMark
Copy link
Member

Describe the enhancement:

As described at #6539 (comment) today when we instantiate the settings for the Collector instance we don't include the components' modules as it is done by upstream's builder.

Describe a specific use case for the enhancement or feature:

This would be primarily useful for the components command.

What is the definition of done?

Populate modules as part of the components and fix components command accordingly.

@ChrsMark ChrsMark added opentelemetry Related to the Elastic Distribution of the OpenTelemetry Collector Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team labels Jan 22, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

@andrzej-stencel
Copy link
Contributor

I think this is an argument to switch to using builder config for the EDOT Collector. This would resolve this issue and also allow users to easily add/remove OTel components to the EDOT Collector.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
opentelemetry Related to the Elastic Distribution of the OpenTelemetry Collector Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team
Projects
None yet
Development

No branches or pull requests

3 participants