VL is really about aggregation, not displaying it. You'd probably just need to setup a grafana dashboard with filters for all your normal traffic
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
What are you using to ship the logs to VL?
If you want to exclude "normal" logs you should start excluding them before they reach VL, so the only logs you have are the interesting ones.
What are you using to ship the logs to VL?
That's the reason I'm here asking about logging. I'm in the process of changing and wondering if I should switch it all up. I was using systemd-journal-remote, but I'm switching from Debian to Alpine so - no more systemd.
you should start excluding them before they reach VL
Now that confuses me. As I said in my original post - I had some preconceptions about centralised logging before I set it up, and having a single place to manage filters was certainly something I was hoping to get from it. Also any filtering would only be for reporting. I'd like to keep a full set of log data for potential problem analysis etc.
In case you decide to look for alternatives, I would probably go with elastic/filebeat/grafana, a fairly standard log monitoring suite. Not saying it’s better or worse than Victoria Logs, which i have no experience with.
I'm already running a grafana instance, so I'll look into elastic/filebeat. Thanks.
Elastic is heaaaaavy. You might want to check out Loki, I haven't used it but I think it'd be easier to get started with than Victoria logs since it integrates tightly with grafana
Yeah, I've been doing some more reading. Victoria Logs is doing a good job consolidating my logs and is very lightweight. It's the visualisation that I'm missing. Grafana can do it, but I'm having trouble getting my head around it. That's OK - it's just my home lab and it's mainly a learning exercise - I need to learn some more.
Yeah I use VL for lemmy.ca and it's super quick and lightweight, but getting what you want into grafana can be difficult.
The more you can filter and label at the source, the less you have to work out in VL.
I use alloy (which is kinda heavy) to extract and prepare only the data I want and it works great so far.