Skip to content

Add comprehensive severity parsing guide for logs pipelines #1537

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jun 25, 2025

Conversation

Calm-Rock
Copy link
Member

@Calm-Rock Calm-Rock commented Jun 6, 2025

Fixes #1488.

- Create detailed guide explaining severity parser processor usage
- Include step-by-step instructions for configuring severity mapping
- Add examples for various log formats and use cases
- Cover special cases like HTTP status code mapping
- Include troubleshooting and best practices

Addresses issue #1488
Copy link

vercel bot commented Jun 6, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
signoz-web ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 20, 2025 11:25am

@Calm-Rock Calm-Rock mentioned this pull request Jun 6, 2025
…ucture

- Use provided example log with nested otel.severity_text structure
- Follow the step-by-step structure from resource guide
- Include the specific cURL request for testing
- Focus only on content from provided references
- Show before/after states for each processor step

Addresses issue #1488
Calm-Rock and others added 2 commits June 20, 2025 12:20
- Remove the cleanup step (step 4) from the guide
- Update the body field to use the cleaner JSON format without escaping
- Keep only the essential 3 steps: JSON Parser, Move, and Severity Parser
- Maintain the same final outcome with parsed_body structure

Addresses issue #1488
Copy link
Contributor

@piyushsingariya piyushsingariya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Calm-Rock Calm-Rock merged commit 1f873f4 into main Jun 25, 2025
2 checks passed
@Calm-Rock Calm-Rock deleted the severity-parsing-guide branch June 25, 2025 11:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Severity parsing guide
2 participants