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

Add configuration bridge to use otel with the elastic environment variables #1619

Open
dmathieu opened this issue Apr 29, 2024 · 2 comments
Open
Labels
agent-go enhancement New feature or request

Comments

@dmathieu
Copy link
Member

Is your feature request related to a problem? Please describe.

Open-source packages currently using this agent recommend customers to use environment variables to configure their instrumentation.
See https://www.elastic.co/guide/en/apm/agent/go/current/configuration.html

We should allow those packages to migrate to otel with no breaking changes. So we should be able to configure otel with the elastic environment variables.

Describe the solution you'd like

A configuration tool, either part of apmotel, or within a new package that would read the elastic documented environment variables, and configure OpenTelemetry with those.

Note: there will still be a change there, as OpenTelemetry doesn't support the Elastic APM protocol, only OTLP.

@dmathieu dmathieu added the enhancement New feature or request label Apr 29, 2024
@jsoriano
Copy link
Member

Note: there will still be a change there, as OpenTelemetry doesn't support the Elastic APM protocol, only OTLP.

Good point. Given this, would still be worth to support migrating with the Elastic environment variables?

@dmathieu
Copy link
Member Author

I think it still may make sense. apm-server does support OTLP. So as long as we document that services can only communicate with recent apm-servers (7.14 and higher it seems), switching to OTLP should be transparent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agent-go enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants