#support

SDK Configuration Error and Exception Traces

TLDR Div shared error traces regarding an SDK configuration and asked if they are related and indicate improper configuration.

9mo

Join the chat

Mar 03, 2023 (9 months ago)

Photo of md5-69a12cc92bad5b259938b070788a11aa

Div

05:17 AM

I am receiving some error traces like this, operation fs readFileSync , just wanted to confirm if this means the configuration for the SDK is not properly done or is it normal ?

Image 1 for I am receiving some error traces like this, operation `fs readFileSync` , just wanted to confirm if this means the configuration for the SDK is not properly done or is it normal ?

05:25

Div

05:25 AM

also I noticed an exception like this

no such file or directory, open '/root/.aws/credentials'
    at Object.openSync (fs.js:498:3)
    at Object.openSync (/var/www/node/node_modules/@opentelemetry/instrumentation-fs/build/src/instrumentation.js:89:33)

could this be related to the above trace ?

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)

Join Our Community

Similar Threads

Issue with SigNoz and OpenTelemetry Instrumentation in NodeJS App

Anshul experienced errors while configuring SigNoz with OpenTelemetry for a NodeJS app. Srikanth suggested using different docs for lambda.

2mo

Issues with Signoz 10.2: Grouping, Missing Traces, and Capturing Requests

Anil reported issues with Signoz 10.2, including grouping, missing traces, and capturing requests. Srikanth suggested upgrading to a newer version. The issue was resolved after upgrading the node version to 18 and additional clarifications were provided.

7mo

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.

9mo