How to ship trace data to a secured collector endpoint ? #3195
Replies: 5 comments 1 reply
-
UDPATE: When I used env variables, I've also adjusted the Env Variables NodeSdk Error in this case:
|
Beta Was this translation helpful? Give feedback.
-
There is a bug in the way opentelemetry-sdk parses the environment variable. You should not have any |
Beta Was this translation helpful? Give feedback.
-
We have the same issue with an external service that uses |
Beta Was this translation helpful? Give feedback.
-
I'm also getting the same issue.
|
Beta Was this translation helpful? Give feedback.
-
Is there a solution to it? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
I have node js application with following dependencies:
My tracing.js which uses Authorization header to send credentials to the secure otlp endpoint
When I run the application :
node --require ./src/tracing.js ./src/service.js
, I receive below error:{"stack":"OTLPExporterError: Not Found\n at IncomingMessage.<anonymous> app-router/node_modules/@opentelemetry/context-async-hooks/build/src/AbstractAsyncHooksContextManager.js:49:55\n at AsyncLocalStorage.run (async_hooks.js:303:14)\n at AsyncLocalStorageContextManager.with (/Users/app-router/node_modules/@opentelemetry/context-async-hooks/build/src/AsyncLocalStorageContextManager.js:33:40)\n at IncomingMessage.contextWrapper (/Users/app-router/node_modules/@opentelemetry/context-async-hooks/build/src/AbstractAsyncHooksContextManager.js:49:32)\n at IncomingMessage.emit (events.js:412:35)\n at endReadableNT (internal/streams/readable.js:1334:12)\n at processTicksAndRejections (internal/process/task_queues.js:82:21)","message":"Not Found","name":"OTLPExporterError","data":"Status: 404\nDescription: Not Found\n","code":"404"}
I have also tried an alternative approach of specifying the credentials via env variables while running the application. It doesn't work either.
OTEL_EXPORTER_OTLP_ENDPOINT=https://<otel-endpoint>
andOTEL_EXPORTER_OTLP_TRACES_HEADERS='Authorization=Basic base64 encoded(username:pwd)'
I'm not sure what is missing in my configuration. Any input appreciated.
Regards,
Santosh
P.S: The setup works fine when shipping traces to a in-secure http endpoint (eg: jeager)
Beta Was this translation helpful? Give feedback.
All reactions