Instrumentation Error with NestJS and Opentelemetry Troubleshooting
TLDR Aniket faced an issue with nestjs instrumentation and Opentelemetry. vishal-signoz suggested downgrading @opentelemetry/exporter-trace-otlp-http to 0.43.0, which resolved the issue.
2
Oct 26, 2023 (1 month ago)
Aniket
09:48 AMInstrumentation 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"}
sudhanshu
10:30 AMsudhanshu
12:05 PMsudhanshu
12:59 PMsudhanshu
12:59 PMsudhanshu
01:02 PM
Piyush
01:13 PMsudhanshu
01:14 PMAniket
01:37 PM "@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-signoz
vishal-signoz
01:45 PM@opentelemetry/exporter-trace-otlp-http to 0.43.0 for now.https://github.com/open-telemetry/opentelemetry-js/issues/4202
Aniket
02:36 PM1
sudhanshu
02:47 PM1
SigNoz Community
Indexed 1023 threads (61% resolved)
Similar Threads
Headers in Monitoring HTTP Endpoints & Otel-Collector Error
Rohit asks about providing headers in monitoring HTTP endpoints and reports errors in otel-collector logs. Srikanth mentions headers are unsupported and requires more investigation for errors.
Error Installing SigNoz on NodeJS App on Graviton Server
abhinav faced errors installing SigNoz on a NodeJS app. vishal-signoz suggested following a workaround on an opentelemetry issue, which resolved the problem.
Troubleshooting SigNoz Auto-Instrumentation Configuration
igor is having trouble configuring auto-instrumentation for Java applications using SigNoz, with traces not appearing in the SigNoz UI. Prashant advises to check logs of the otel sidecar, use service name for endpoint, verify supported libraries, and test with telemetrygen. However, the issue still persists.
Displaying MongoDB Atlas Metrics on Signoz Dashboard
Div is unable to display MongoDB Atlas query time data on Signoz Dashboard. Ankit and vishal-signoz suggest checking compatible versions and using different packages, but the issue remains unresolved.
NestJS Installation and Data Populating in SignOz Dashboard
abhinav had an issue with NestJS data not populating in their SignOz dashboard. vishal-signoz recommended updating otel versions in package.json, which resolved the issue.