You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My problem is that the target pods are producing logs in a variety of formats that do not conform with the parser, many of which I do not care for. Those logs effective skip the parser.
Is there a way for me to entirely trop those logs if they do not match the parser?
At the moment, I need to write a filter for every possible log format they produce, e.g.
[FILTER]name grepmatch *# These are low value/high noise (LVHN) logs produced by airbyte workers# https://regex101.com/r/IIFK6X/1exclude log /^Log4j2Appender says:/# following by many more exclude rules...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've configured a parser using Kubernetes labels:
The parser itself looks like so:
My problem is that the target pods are producing logs in a variety of formats that do not conform with the parser, many of which I do not care for. Those logs effective skip the parser.
Is there a way for me to entirely trop those logs if they do not match the parser?
At the moment, I need to write a filter for every possible log format they produce, e.g.
which feels like a losing battle
Beta Was this translation helpful? Give feedback.
All reactions