Issue with SigNoz and OpenTelemetry Instrumentation in NodeJS App
TLDR Anshul experienced errors while configuring SigNoz with OpenTelemetry for a NodeJS app. Srikanth suggested using different docs for lambda.
Powered by Struct AI
2
2mo
Solved
Sep 28, 2023 (2 months ago)
Anshul
Anshul
01:17 PMHi
I am trying out signoz with opentelemetry for my nodejs application
My signoz is on cloud platform and while trying to start the appliction i am getting error
Unable to initialize instrumentation for lambda. Cannot identify lambda handler or task root. { taskRoot: undefined, handlerDef: undefined }
@opentelemetry/instrumentation-grpc Module @grpc/grpc-js has been loaded before @opentelemetry/instrumentation-grpc so it might not work, please initialize it before requiring @grpc/grpc-js
OpenTelemetry automatic instrumentation started successfully
no original function cpSync to wrap
no original function cp to wrap
no original function cp to wrap
Process is not running on K8S [Error: ENOENT: no such file or directory, access '/var/run/secrets/kubernetes.io/serviceaccount/token'] {
errno: -2,
code: 'ENOENT',
syscall: 'access',
path: '/var/run/secrets/kubernetes.io/serviceaccount/token'
}
{message":"Not Allowed","name":"OTLPExporterError","data":"<html>\r\n<head><title>405 Not Allowed</title></head>\r\n<body>\r\n<center><h1>405 Not Allowed</h1></center>\r\n<hr><center>nginx/1.25.2</center>\r\n</body>\r\n</html>\r\n","code":"405"}
and no logs are found on the signoz UI itself
I am trying out signoz with opentelemetry for my nodejs application
My signoz is on cloud platform and while trying to start the appliction i am getting error
Unable to initialize instrumentation for lambda. Cannot identify lambda handler or task root. { taskRoot: undefined, handlerDef: undefined }
@opentelemetry/instrumentation-grpc Module @grpc/grpc-js has been loaded before @opentelemetry/instrumentation-grpc so it might not work, please initialize it before requiring @grpc/grpc-js
OpenTelemetry automatic instrumentation started successfully
no original function cpSync to wrap
no original function cp to wrap
no original function cp to wrap
Process is not running on K8S [Error: ENOENT: no such file or directory, access '/var/run/secrets/kubernetes.io/serviceaccount/token'] {
errno: -2,
code: 'ENOENT',
syscall: 'access',
path: '/var/run/secrets/kubernetes.io/serviceaccount/token'
}
{message":"Not Allowed","name":"OTLPExporterError","data":"<html>\r\n<head><title>405 Not Allowed</title></head>\r\n<body>\r\n<center><h1>405 Not Allowed</h1></center>\r\n<hr><center>nginx/1.25.2</center>\r\n</body>\r\n</html>\r\n","code":"405"}
and no logs are found on the signoz UI itself
Sep 29, 2023 (2 months ago)
Srikanth
Srikanth
01:48 AMYou can’t use the same docs for lambda. Please see https://github.com/open-telemetry/opentelemetry-lambda
SigNoz Community
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI
Indexed 1023 threads (61% resolved)
Similar Threads
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.
13
9mo
Solved
Resolving SigNoz v.0.22 Crash for Python Application
COMER reports a SigNoz v.0.22 crash with their Python app. Despite Srikanth's troubleshooting suggestions and confirmation that their application runs fine without `opentelemetry-instrument`, the cause of the problem remains unclear.
27
1mo
Troubleshooting Django App Instrumentation with Signoz
tim encountered issues instrumenting a Django app with Signoz. tim resolved the problem by identifying the need for a client to forward content to Signoz.
12
6mo
Solved