https://signoz.io logo
Join Slack
Powered by
Evening, is there a way to map severity_text when ...
# support
g
Evening, is there a way to map severity_text when data is being ingested? I want all log messages that are at the same severity level, but have different case or short form of the severity text, e.g. 
INFO
vs 
info
vs 
Information
vs 
INFORMATION
, to be displayed when selecting the value I choose to map these to. So, for example in the image below, I just want one 
Information
, 
Warning
, 
Error
, 
Critical
and 
Debug
severity text levels and when selected to show all log messages at that level. I'd also like to be able to update all logs that have already been ingested.
I think I have found the answer, except I can't seem to get it to work (OR my understanding of what I should see is incorrect). Appears I should be using the severity parser pipeline processor - https://signoz.io/docs/logs-pipelines/processors/#severity-parser. I've set up the filter, add the processor with mappings as per the image below. But the logs still contain the value 
Information
for severity_text. Shouldn't the severity_text be updated to 
INFO
?
I'm using SigNoz version 0.56.0
@nitya-signoz I see you're answering some questions. Any hint on what I'm doing wrong with setting up a severity parser processor?
n
Interesting, so you are having different values of severity i.e 
error/ERROR
and you want to group it to same. The above parser that you shared won’t work here as severity_text is not really an attribute. @Raj Kamal will be the right person to help you here.
r
Hi Greg 🙂 As Nitya mentioned, unfortunately, there is no way to target the severity_text of a log in a pipeline processor's "parse from" field I have added an issue for this in our backlog and will release an update to address this need as soon as we can
g
Thanks @Raj Kamal and @nitya-signoz.
22 Views
Open in Slack
PreviousNext
Powered by