Anybody running Cacti with Pi-hole?

I'm looking at monitoring my cable modem, ISP and my work VPN in order to determine the point of failure when I experience latency issues with work.

I was looking to see the best way to monitor and I ran across Cacti. Is anybody else running it along side Pi-hole? I notice that it supports lighttpd which is already running since that's what Pi-hole uses, but I didn't want to break anything when installing it. Anybody else running this configuration?

I'm personally using SmokePing for basic latency monitoring but I don't see why Cacti wouldn't work as well. It's separate from Pi-hole in everything other than they share a webserver.

You should probably change where you put Cacti's web interface to avoid conflict with Pi-hole's blocking page. If you put it in /var/www/Cacti you need to tell lighttpd that that is where the files are by adding this snippet to /etc/lighttpd/external.conf:

$HTTP["host"] =~ "cacti" {
	server.document-root = "/var/www/Cacti/"

(Capitalization matters)
Then create a DNS entry in Pi-hole (Local DNS > DNS Records) for cacti.localdomain pointing to your server (of course replace localdomain with the actual domain on your LAN). That's the domain that will get you to Cacti's web interface.

I think the rest of the installation process is pretty much independent of Pi-hole.

Thanks @Daxtorim. I'll check out SmokePing too!

I've checked out SmokePing. What about Icinga? I'd like to ping and also capture packet loss data to the targets I want to monitor both inside my network (cable modem) and outside (work vpn). Anybody have any other suggestions that would play well with Pi-hole?

Traceroute NG looks to be perfect for what I'm needing, but doesn't appear to support raspbian.

No additional suggestions?

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.