Reducing Telemetry Logs in Pod Logging
TLDR Pocho is experiencing an issue with excessive telemetry logs using opentelemetry-instrument. Srikanth requests a sample to further investigate.
Jun 08, 2023 (6 months ago)
Pocho
04:19 PMopentelemetry-instrument command, the pod logs get filled with telemetary logs and we’re missing some app logs in stream as it’s too chatty. Anyway to reduce that? Setting the log_level didn’t seem to have any impact. thx!Jun 12, 2023 (6 months ago)
Srikanth
01:05 AMThere is a very minimal telemetry logging and they shouldn’t be chatty. Can you share the sample here?
SigNoz Community
Indexed 1023 threads (61% resolved)
Similar Threads
Otel-collector Pods Stuck in Running State
Guillaume experienced an issue where pods remained in 'Running' state but not 'Ready' status. Srikanth suggested potential connection issues with ClickHouse. The issue resolved itself after some time, with no changes made.
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.
Slow Log Messages in SigNoz with Logrus and OpenTelemetry
Harald reported slow log messages in SigNoz with logrus and open telemetry. They narrowed down the problem to focusing on relevant k8s namespaces, which improved performance to near real-time.