[CFR][CFT] counter(9): new API for faster and raceless counters

Alfred Perlstein alfred at ixsystems.com
Thu Apr 4 16:04:10 UTC 2013

Since we're taking the "blunt route" I'll be blunt as well:

You have completely missed the point of the project I am working on.

Here is the point which you have missed:

I was attempting to graph as many stats as possible, in addition I was 
looking at some heuristics to find out when machines go bad. In doing so 
I found that the user land utilities are require quite a bit of parsing 
to figure this stuff out due to varied output formats.

Both Munin and Graphite suffer from this as well.  Go read through the 
plugins (which lack many of the metrics I've pulled in a generic 
fashion) and you'll see what I'm talking about.

What we are inventing and proposing is adding output options for various 
tools in the base system to better plug into these monitoring tools.

This means a CSV/XML-like output for tools like sysctl/netstat/etc/etc 
and I was probing the community for feedback on this matter.

What I was not looking for was a pat on the back for the graphing system 
we worked on for a total of 5 days.

I hope this helps.


On 4/4/13 1:59 AM, Dag-Erling Smørgrav wrote:
> Alfred Perlstein <alfred at ixsystems.com> writes:
>> Here at iXsystems we've just developed a set of scripts to scrape the
>> various FreeBSD user land utilities (sysctl, netstat, nfsstat, vmstat,
>> etc, etc) and put them into graphs based on time.
> in other words, you've reinvented Munin and Graphite?
>> The only problem we have is that every user land tool has its own
>> format, so along with my team we have written some shell to coerce the
>> output from the various programs into pseudo-CSV (key/value pair)
>> which can then be post processed by tools to convert to CSV which can
>> then be put into something like open office, or put through an R
>> program to graph it.
> in other words, you've reinvented rrdtool?

More information about the freebsd-arch mailing list