#support

Issue with Logging Severity Number in Signoz

TLDR Matt raised an issue with severity_number getting logged as '0' in Signoz. nitya-signoz suggested using the severity parser for resolution.

Join the chat

Nov 06, 2023 (3 weeks ago)

Photo of md5-03880c889015cc418dc9a43f1f477eb0

Matt

08:15 PM

but still no luck. The body has severity_number: 8 but the log entry in signoz is still showing severity_number: 0

Nov 07, 2023 (3 weeks ago)

Photo of md5-a52b9d6c34f193d9a1ff940024f36f77

nitya-signoz

11:10 AM

You will have to use the severity parser https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/stanza/docs/types/severity.md

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

SigNoz Log Format and JSON Parsing

Luke asked about the log format for SigNoz and using operators to convert loggers. nitya-signoz shared resources about specifications and recommended using operators. Travis had issues with JSON parsing but resolved them by updating `otel-agent-config.yaml`.

9mo

Problem with Parsing Large JSON Logs

Saad asks for help with Signoz parsing large JSON logs into multiple logs. nitya-signoz suggests changing `max_log_size`, but the exact configuration steps are left unclear.

yesterday

Parsing JSON Logs in Kubernetes for Different Applications

Nick sought advice on parsing JSON logs in Kubernetes for apps without OTEL support. nitya-signoz suggested using additional operators, creating pipelines, and mapping according to the business logic.

8mo