Date: Wed, 24 Sep 2014 17:16:14 +0200 From: Borja Marcos <borjamar@sarenet.es> To: "freebsd-performance@FreeBSD.org" <freebsd-performance@FreeBSD.org> Subject: Re: I like iostat, but... Message-ID: <5DBB0BDC-92FB-44FF-8869-67CFA2B52C26@sarenet.es> In-Reply-To: <20140924150915.GC1221@albert.catwhisker.org> References: <20140924150915.GC1221@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 24/9/2014, at 17:09, David Wolfskill <david@catwhisker.org> wrote: >=20 >=20 >> On Tue, Sep 23, 2014 at 10:45:14AM +0200, Borja Marcos wrote: >> ...=20 >> Anyway, for disk stats GEOM offers a nice API. You can get delays per GEO= M provider, bandwidths, etc. >=20 >>=20 >=20 >=20 > Folks, I appreciate the suggestions, but they address problems other > than the one I am trying to solve. >=20 > In particular: > * I require that the tool must only depend on components of base FreeBSD; > thus, I don't need to perturb the system I want to measure by > installing otherwise unneeded software on it. Devilator has no dependencies. It reads sysctl and geom. >=20 > Basically, I have something that works "well enough" for things > like CPU counters, memory usage (at the rather coarse granularity > that top(1) provides, vs. "vmstat -m" output), load avergaes, and > NIC counters, and is readily extensible to any univariate (or simple > list of multivariate) (non-opaque) sysctl OIDs. I'd like to be > able to include information from the I/O subsystem -- in particular, > data that is accessible from "iostat -x". Check the diskbw.c module. Actually Most of it is borrowed from gstat(8). Ju= st format the output data as you wish ;) But you don't need Orca. The agent just creates text files.=20 Cheers, Borja.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5DBB0BDC-92FB-44FF-8869-67CFA2B52C26>