Monitoring

Did VictoriaLogs miss any logs during the reboot?

Leave a Comment / FreeBSD, Monitoring, Network monitoring, Open Source, syslog-ng, Victoria Logs / By /

Yesterday, I modified r730-01 by Running pkgbasify on FreeBSD 15.0 – as a consequence, my log collecting jail was offline. Did it miss any logs? Let’s find out. In this post: FreeBSD 15.0 syslog-ng-4.11.0_2 (sending logs from FreshPorts production) victoria-logs-1.50.0_2 (receiving logs in the logs jail The period in question Looking at /var/log/messages, I see: With syslogd now stopped, there are no further logs until: NOTE: I had not set the logs jail […]

Did VictoriaLogs miss any logs during the reboot? Read More »

Adding syslog-ng to a host to extract Nginx logs

Leave a Comment / FreeBSD, Monitoring, Open Source, syslog-ng, Victoria Logs / By /

This replaces and combines two earlier posts: Replacing syslogd with syslog-ng (sysutils/syslog-ng) on FreeBSD. Getting Nginx logs into Victoria-Logs I just got Victoria Logs running. Now I want to get logs into it. For starters, I want to get the logs on the host itself into Victoria Logs. I figure this is a log-risk experiment. In this post: FreeBSD 15.0 victoria-logs-1.50.0_2 syslog-ng-4.11.0_2 I’m installing syslog-ng on a host (x8dtu) The nginx logs reside

Adding syslog-ng to a host to extract Nginx logs Read More »

Getting Nginx logs into Victoria-Logs – v2

Leave a Comment / FreeBSD, Monitoring, nginx, Open Source, syslog-ng, Victoria Logs / By /

VictoriaLogs is feature rich, which means at this point, I know very little about it. However, this post has been deprecated by a newer post which covers more material. I do know that the original syslog-ng configuration I supplied in Getting Nginx logs into Victoria-Logs is now less complicated. With the help of duck.ai, I managed to reduce it. Now it’s sending the json without running it through a parser. In this post:

Getting Nginx logs into Victoria-Logs – v2 Read More »

VictoriaLogs: Adding syslog-ng to a host and ingesting nginx log from jails

Leave a Comment / FreeBSD, Monitoring, nginx, Open Source, syslog-ng, Victoria Logs / By /

This post is more self-documentation than anything else. The links in this post might be useful than the content. However, this post has been deprecated by a newer post which covers more material. Today I’ll start pulling production FreshPorts nginx logs into VictoriaLogs. Over the past few days, I’ve configured a proof-of-concept and now I’m ready to try this in prod. In this post: FreeBSD 15.0 (installed on the host aws-1) nginx-1.30.2_2,3 (running

VictoriaLogs: Adding syslog-ng to a host and ingesting nginx log from jails Read More »

Getting Nginx logs into Victoria-Logs

Leave a Comment / FreeBSD, Monitoring, Open Source, syslog-ng, Victoria Logs / By /

My goal today: get nginx logs into Victoria-Logs. I’ve already gotten Victoria-Logs running on FreeBSD and replaced syslog with syslog-ng to get TLS NOTE: This post was originally only about Nginx. I’ve since added general syslog messages to the configuration. However, this post has been deprecated by a newer post which covers more material. Also, the Adding an nginx proxy in front of Victoria-Labs post might be helpful before proceeding here. Over the

Getting Nginx logs into Victoria-Logs Read More »

Adding an nginx proxy in front of Victoria-Labs

Leave a Comment / FreeBSD, Monitoring, nginx, Open Source, Victoria Logs / By /

Victoria-Logs has an built-in UI – and it’s easier for me to access via my web browser if I put Nginx in front of it. In this post: FreeBSD 15.0 victoria-logs-1.50.0_2 nginx-1.30.2_2,3/li> Victoria Logs config This is the main configuration, as found in /etc/rc.conf: Those \ and multiple lines, yea, don’t do that, put it all on one line. I’ve done that above to make it easier for you to read. Nginx This

Adding an nginx proxy in front of Victoria-Labs Read More »

Replacing syslogd with syslog-ng (sysutils/syslog-ng) on FreeBSD

Leave a Comment / syslog-ng / By /

I just got Victoria Logs running. Now I want to get logs into it. For starters, I want to get the logs on the host itself into Victoria Logs. I figure this is a log-risk experiment. However, this post has been deprecated by a newer post which covers more material. In this post: FreeBSD 15.0 victoria-logs-1.50.0_2 syslog-ng-4.11.0_2 I will be using TLS between syslog-ng and victoria-logs – you will notice this is all

Replacing syslogd with syslog-ng (sysutils/syslog-ng) on FreeBSD Read More »

LibreNMS 26.6.0 & itable cache directories vntl/var/db/

Leave a Comment / FreeBSD, LibreNMS, Monitoring, Open Source / By /

I updated my version of LibreNMS to 26.6.0 and there are “decent sized refactor to the rrd processes” – I’m seeing the following: This is an issue with fontconfig The advice I was given: “XDG_CACHE_HOME might help, but I’m not sure if that is the right fix…” I first created a new directory (I’ve since discovered creating the directory is not necessary, adding the configuration item is sufficient): [12:45 besser dvl /var/db/librenms] %

LibreNMS 26.6.0 & itable cache directories vntl/var/db/ Read More »

LibreNMS Service health file disabled

Leave a Comment / LibreNMS, Open Source / By /

There is no solution here. I’m merely documenting. I use LibreNMS for metrics. Recently, a new item has appeared in the logs: Apr 17 00:00:17 besser librenms[81601]: besser.int.unixathome.org(INFO):Service health file disabled. Checking the code, I found the reference on line 422 of LibreNMS/service.py: Searching for health_file, I found: Which tells me I can set this in my configuration. Searching files: [11:21 besser dvl /usr/local/www/librenms] % grep -ril service_health_file * LibreNMS/service.py app/Console/Commands/HealthCheck.php html/js/lang/en.js lang/en/settings.php

LibreNMS Service health file disabled Read More »

network connectivity issues – in the #homelab

Leave a Comment / Network monitoring, Networks / By /

Yesterday a big storm came through. Many downed trees (photos here). The power went off at about 0500 and came back again at about 1009, off again at 1309, back at 1319. It was then stable for the rest of the day. Overnight, I saw monitoring alerts which initially made me think there was another power cut. uptime showed that was not the case. I also didn’t see any timeout messages meaning the

network connectivity issues – in the #homelab Read More »

Scroll to Top