#support

Issue With SDK Object Data

TLDR Kewal reported a discrepancy in SDK object data in his app versus the sample app. Srikanth advised verifying the SDK version.

3mo

Join the chat

Aug 17, 2023 (3 months ago)

Photo of md5-2f94b63d050dad6ced4a85316a658c61

Kewal

09:05 AM

when i print sdk object i get : _resourceDetectors: [ EnvDetector {}, ProcessDetector {} ],

While the same object in sample app project is not empty.

Photo of md5-ce04a9988e2fd758a659dc55be6f2543

Srikanth

01:48 PM

Please make sure you are using the correct version of SDK

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

Field Name Discrepancy in OTEL Collector

manohar reported a naming discrepancy for the same parameter in their source records when using version 0.55.0 of the OTEL collector, and asked if this issue has been resolved in the agent or had similar cases. The thread ends without resolution.

5mo

Issue Accessing Pod Logs in SigNoz UI on AKS

prashant is facing an issue accessing pod logs of their application in SigNoz UI on AKS. nitya-signoz and Prashant provide suggestions related to log file paths and potential issues, but the problem remains unresolved.

6mo

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.

8mo