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

opentelemetry-bridge should use the ELASTIC_APM_API_KEY #4039

Open
itay-ct opened this issue May 25, 2024 · 1 comment
Open

opentelemetry-bridge should use the ELASTIC_APM_API_KEY #4039

itay-ct opened this issue May 25, 2024 · 1 comment
Assignees

Comments

@itay-ct
Copy link

itay-ct commented May 25, 2024

current docs for opentelemetry-bridge example use ELASTIC_APM_SECRET_TOKEN but recent versions prefer ELASTIC_APM_API_KEY otherwise 'unsupported authorization scheme' is raised. Docs/README should be updated.

@trentm trentm added the triage label Jun 4, 2024
@trentm trentm self-assigned this Jun 4, 2024
@trentm
Copy link
Member

trentm commented Jun 4, 2024

Hi @itay-ct,
Are you referring to step (2) at https://www.elastic.co/guide/en/apm/agent/nodejs/current/opentelemetry-bridge.html#otel-tracing-api?

Screenshot 2024-06-04 at 2 10 30 PM

Docs/README should be updated.

Oh, or do you mean it feels like time to update all relevant user-guide and getting-started docs to prefer auth using API key rather that secretToken, given API key is the only one that works for both types of cloud-hosted stack?

but recent versions prefer ELASTIC_APM_API_KEY

And by recent versions, do you mean Elastic Cloud Serverless projects? IIUC, those only support API key auth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants