2 ms·
We did setup Cacti but we were wanting to focus on tracking data particularly about the CPU of each server, as well as 1 particular process running on it. For t
by Skywing 16y ago
We did setup Cacti but we were wanting to focus on tracking data particularly about the CPU of each server, as well as 1 particular process running on it. For that process, we wanted to track various stats like thread count, open network connections by it, open files by it, etc. We also wanted to monitor some environment metrics. The system we wrote is simply a Python app running under a cron job, reporting this data to our database server(s). We're going to be adding some notification type functionality to it so that we will be notified if things go awry, which they tend to do at least once a week. :(
I'm pleased with out data collecting setup - it's working well. But, obviously the power is in the reporting which is what we will be working on this upcoming week. I'm just researching the best methods for doing this in a scalable manner.
- jerf 16y agoIt's still somewhat unclear to me how Cacti is deficient. You know it can track anything, right, not just what it ships with out of the box? I have a chat-like server process that holds open TCP streams to clients indefinitely, and we wrote something to feed Cacti that number, and it tracks it like any other. I don't know how the internals look so I don't know whether it ends up being useful for other uses or not. The other thing you probably ought to specify is the frequency of the reports and what you want them to be reporting on. On a decently-spec'ed system it just doesn't seem like you're really talking about that much data here, you should probably try to be more clear where your bottleneck is. And you should probably head to some community that can pay attention to something like this for a longer period of time, a forum or a newsgroup or something.