Issues with Signoz Update and Opentelemetry-Operator Version
TLDR oluchi experiences errors after updating Signoz and opentelemetry-operator. Prashant suggests downgrading to v0.70.X, and oluchi agrees to test it out.
1
1
1Apr 13, 2023 (5 months ago)
oluchi
01:01 PMWe currently updated our signoz application to the latest version, also with the
opentelemetry-operator to the lastest, but we are currently battling some errors with our node applications.otel-auto-instrumentation/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:75
throw new Error(`PeriodicExportingMetricReader: metrics export failed (error ${result.error})`);
^
Error: PeriodicExportingMetricReader: metrics export failed (error Error: 14 UNAVAILABLE: No connection established)
at doExport (/otel-auto-instrumentation/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:75:23)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)Please what is the supported
opentelemetry-operator version that currently supports v0.18.1 Signoz version?
Prashant
01:20 PMOfficially we support v0.66.X version.
However, I have personally tested v0.70.X and didn't face any issues.
11Prashant
01:21 PMopentelemetry-operator to v0.70.X and test it out?oluchi
01:22 PM1
SigNoz Community
Indexed 825 threads (61% resolved)
Similar Threads
Issues and Changes in OpentelemetryJs
Harald expressed frustration about changes and documentation issues in OpentelemetryJs. Srikanth shared the upgrade guidelines and suggested contributing to improve the project. Harald agreed to create a new PR for SigNoz examples.
1Troubleshooting Signoz Dashboard Not Showing Traces
prasanth encountered issues with Signoz dashboard not displaying traces. Srikanth recommended configuring the `OTEL_EXPORTER_OTLP_ENDPOINT`, but they are still facing issues with the exporter's connection.
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.