Feat: QS: logs pipelines severity parsing processor #4132
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
raj-k-singh
force-pushed
the
feat/qs/logs-pipelines-severity-parsing-processor
branch
from
b9107a2
to
60a0661
Compare
srikanthccv
reviewed
Dec 1, 2023
|
Just one comment about the valid based on the OTLP logs protocol. I am not sure if the upstream parser supports them. Otherwise, LGTM. |
The upstream parser supports trace and fatal. Have made the change. Please take a look again @srikanthccv |
srikanthccv
approved these changes
Dec 1, 2023
raj-k-singh
deleted the
feat/qs/logs-pipelines-severity-parsing-processor
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds query service support for severity parsing processor
Related Issues / PR's
Contributes to #4060