Skip to content
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

[Feat]: ability to in some way filter or ignore known log messages from systemd-journal logs UI #975

Open
andrewm4894 opened this issue Jan 25, 2024 · 0 comments

Comments

@andrewm4894
Copy link

Problem

I have some common known error messages in my logs that i am happy to have found but totally ok just ignoring them. so i would like to remove trhem from the picture in the netdata systemd journal logs UI in some way so that i can rely on it for more interesting and new or "unknown" log messages.

for example in below image i have the gcp monitoring agent having issues regulalry since its missing some permission. its great to be able to easily surface this but i now decide i dont care and so would like to filter these logs in some way out of my "clean" view in the netdata ui.

image

Description

am thinking some sort of basic regex in the netdata ui or as cloud pulls the data could be really useful.

eg if i could build up a set of filter rules, kinda like gmail filters or lots of other stuff like this, then it could be cool to just be able to, right within the netdata UI, in the moment, just define a rule to "handle" (include or exclude but you could imagine other actions to take too maybe longer term) any log lines that match.

a view over my logs then can just be a set of such rules.

in fact this need not just be about my use case here - maybe could be more general too since you could for example make a few rules to get all database related logs and save that as a different view etc.

Importance

really want

Value proposition

  1. ability to make the systemd-journal logs more like a clean and maintained view and build some of my own domain understanding into it.

Proposed implementation

i guess the filtering and processing of these rules would be the potentially tricky part. if could be pushed down to the agent that that could be really cool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant