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
Is your feature request related to a problem? Please describe.
It is hard to parse the output of popeye with log parser when running it unattended in a kubernetes cluster. The JSON output is hard to parse since all linter infos are in an array and it seems impossible to extract labels.
A nice parseable logfmt output with predefined labels like namespace, linter, testname, type, testid and the message would make it easy to create dashboards with logql parsing.
Describe the solution you'd like
Add logfmt output that shows each linter result as a single logline with predefined labels
Describe alternatives you've considered
Parsing json logs -> Hard to achive
using cli logs -> parsing is hard and context is not given
Additional context
Useful in multiteant k8s environements to give each tenant access to their findings.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It is hard to parse the output of popeye with log parser when running it unattended in a kubernetes cluster. The JSON output is hard to parse since all linter infos are in an array and it seems impossible to extract labels.
A nice parseable logfmt output with predefined labels like namespace, linter, testname, type, testid and the message would make it easy to create dashboards with logql parsing.
Describe the solution you'd like
Add logfmt output that shows each linter result as a single logline with predefined labels
Describe alternatives you've considered
Parsing json logs -> Hard to achive
using cli logs -> parsing is hard and context is not given
Additional context
Useful in multiteant k8s environements to give each tenant access to their findings.
The text was updated successfully, but these errors were encountered: