I an facing the following error when trying to set...
# support
a
I an facing the following error when trying to setup instrumentation in nestjs (I am following https://signoz.io/docs/instrumentation/nestjs/#validating-instrumentation-by-checking-for-traces for reference):
Copy code
Instrumentation suppressed, returning Noop Span
@opentelemetry/instrumentation-http http instrumentation outgoingRequest
@opentelemetry/instrumentation-http http.ClientRequest return request
{"stack":"OTLPExporterError: Bad Request\n    at IncomingMessage.<anonymous> (/Users/piyushonkar/Desktop/CodeBase/remittance/node_modules/@opentelemetry/otlp-exporter-base/src/platform/node/util.ts:131:27)\n    at /Users/piyushonkar/Desktop/CodeBase/remittance/node_modules/@opentelemetry/context-async-hooks/src/AbstractAsyncHooksContextManager.ts:75:49\n    at AsyncLocalStorage.run (node:async_hooks:335:14)\n    at AsyncLocalStorageContextManager.with (/Users/piyushonkar/Desktop/CodeBase/remittance/node_modules/@opentelemetry/context-async-hooks/src/AsyncLocalStorageContextManager.ts:40:36)\n    at IncomingMessage.contextWrapper (/Users/piyushonkar/Desktop/CodeBase/remittance/node_modules/@opentelemetry/context-async-hooks/src/AbstractAsyncHooksContextManager.ts:75:26)\n    at IncomingMessage.emit (node:events:526:35)\n    at endReadableNT (node:internal/streams/readable:1376:12)\n    at processTicksAndRejections (node:internal/process/task_queues:82:21)","message":"Bad Request","name":"OTLPExporterError","data":"{\"code\":3,\"message\":\"ReadUint64: unsupported value type, error found in #10 byte of ...|UnixNano\\\":{\\\"low\\\":-14|..., bigger context ...|\\\"name\\\":\\\"tcp.connect\\\",\\\"kind\\\":1,\\\"startTimeUnixNano\\\":{\\\"low\\\":-1400614016,\\\"high\\\":395419195},\\\"endTimeUnixN|...\"}","code":"400"}
@opentelemetry/instrumentation-http outgoingRequest on response()
@opentelemetry/instrumentation-http outgoingRequest on end()
@opentelemetry/instrumentation-http outgoingRequest on request close()
{"stack":"OTLPExporterError: Bad Request\n    at IncomingMessage.<anonymous> (/Users/piyushonkar/Desktop/CodeBase/remittance/node_modules/@opentelemetry/otlp-exporter-base/src/platform/node/util.ts:131:27)\n    at /Users/piyushonkar/Desktop/CodeBase/remittance/node_modules/@opentelemetry/context-async-hooks/src/AbstractAsyncHooksContextManager.ts:75:49\n    at AsyncLocalStorage.run (node:async_hooks:335:14)\n    at AsyncLocalStorageContextManager.with (/Users/piyushonkar/Desktop/CodeBase/remittance/node_modules/@opentelemetry/context-async-hooks/src/AsyncLocalStorageContextManager.ts:40:36)\n    at IncomingMessage.contextWrapper (/Users/piyushonkar/Desktop/CodeBase/remittance/node_modules/@opentelemetry/context-async-hooks/src/AbstractAsyncHooksContextManager.ts:75:26)\n    at IncomingMessage.emit (node:events:526:35)\n    at endReadableNT (node:internal/streams/readable:1376:12)\n    at processTicksAndRejections (node:internal/process/task_queues:82:21)","message":"Bad Request","name":"OTLPExporterError","data":"{\"code\":3,\"message\":\"ReadUint64: unsupported value type, error found in #10 byte of ...|UnixNano\\\":{\\\"low\\\":-10|..., bigger context ...|e\\\":\\\"fs realpathSync\\\",\\\"kind\\\":1,\\\"startTimeUnixNano\\\":{\\\"low\\\":-1031614016,\\\"high\\\":395419195},\\\"endTimeUnixN|...\"}","code":"400"}
s
We are sending the APM on port 4318
@Ankit Anand Any idea on it. We are following your doc
@Aniket Singh Plz share package.json
@Vishal Sharma will help us
@Piyush Onkar Plz share the package.json
p
package.json
s
@Vishal Sharma plz look
a
Copy code
"@opentelemetry/auto-instrumentations-node": "^0.39.4",
    "@opentelemetry/exporter-trace-otlp-http": "^0.44.0",
    "@opentelemetry/sdk-node": "^0.44.0",
    "@opentelemetry/semantic-conventions": "^1.17.1",
We are using the above otel dependencies with respective versions @Vishal Sharma
v
@Aniket Singh There’s reported issue with v0.44. try downgrading
@opentelemetry/exporter-trace-otlp-http
to
0.43.0
for now. https://github.com/open-telemetry/opentelemetry-js/issues/4202
a
Thanks @Vishal Sharma, this helped. We are able to send traces now
s
Thank you @Vishal Sharma for quick help