Signoz Deployment Error: Unsupported Metric Type
TLDR Einav is having trouble with a signoz deployment, receiving an error regarding unsupported metric types. Srikanth suggests they may be encountering a known error and provides a link for reference.
Jul 31, 2023 (4 months ago)
Einav
11:06 AMi'm having trouble with signoz deployment (helm chart 0.21.0)
otel collector show messages suc has
2023-07-31T10:55:05.548Z error exporterhelper/queued_retry.go:391 Exporting failed. The error is not retryable. Dropping data. {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "Permanent error: unsupported metric type; Permanent error: unsupported metric type; Permanent error: unsupported metric type; Permanent error: unsupported metric type", "errorCauses": [{"error": "Permanent error: unsupported metric type"}, {"error": "Permanent error: unsupported metric type"}, {"error": "Permanent error: unsupported metric type"}, {"error": "Permanent error: unsupported metric type"}], "dropped_items": 6738}
/home/runner/go/pkg/mod/go.opentelemetry.io/collector/[email protected]/exporterhelper/queued_retry.go:391
/home/runner/go/pkg/mod/go.opentelemetry.io/collector/[email protected]/exporterhelper/metrics.go:125
/home/runner/go/pkg/mod/go.opentelemetry.io/collector/[email protected]/exporterhelper/queued_retry.go:195
/home/runner/go/pkg/mod/go.opentelemetry.io/collector/exp[email protected]/exporterhelper/internal/bounded_memory_queue.go:47
agent logs
2023-07-31T10:54:12.677Z info exporterhelper/queued_retry.go:423 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "otlp", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp 1signoz-otel-collector:4317: connect: connection refused\"", "interval": "10.268880523s"}
2023-07-31T10:54:22.948Z info exporterhelper/queued_retry.go:423 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "otlp", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp signoz-otel-collector:4317: connect: connection refused\"", "interval": "37.016329507s"}
clickhouse memory usage is above 30Gb
the cluster is rather stale and has no much going on there, yet it looks like the whole stack is overflowed
any ideas?
Srikanth
11:48 AMEinav
01:13 PMSigNoz Community
Indexed 1023 threads (61% resolved)
Similar Threads
Resolving Signoz Query Service Error
Einav encountered an error related to a missing table in the Signoz service which was preventing data visibility in the UI. Srikanth guided them to restart specific components and drop a database table, which resolved the issue.
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.
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.