On 9/24/14 8:09 AM, David Wolfskill wrote:
On Tue, Sep 23, 2014 at 12:29:22AM +0300, Andriy Gapon wrote:
On 23/09/2014 00:22, David Wolfskill wrote:
... I rather wish I could get the same information via sysctl. (Well,
something seems to be available via the "opaque" kern.devstat.all
sysctl(8
> On 24/9/2014, at 17:09, David Wolfskill wrote:
>
>
>> On Tue, Sep 23, 2014 at 10:45:14AM +0200, Borja Marcos wrote:
>> ...
>> Anyway, for disk stats GEOM offers a nice API. You can get delays per GEOM
>> provider, bandwidths, etc.
>
>>
>
>
> Folks, I appreciate the suggestions, but t
On Tue, Sep 23, 2014 at 12:29:22AM +0300, Andriy Gapon wrote:
> On 23/09/2014 00:22, David Wolfskill wrote:
> > ... I rather wish I could get the same information via sysctl. (Well,
> > something seems to be available via the "opaque" kern.devstat.all
> > sysctl(8) variable, but sysctl(8) doesn't
> If the shock of reading atrocious code won't make you pull your eyes out of
> your sockets I
> can send you the latest version of devilator a FreeBSD specific data
> collector for Orca
> (https://www.orcaware.com/orca/).
sure. Im still thinking how to improve things on my side. Im not C fluen
On Sep 23, 2014, at 11:19 AM, Stefan Parvu wrote:
>
>> Anyway, for disk stats GEOM offers a nice API. You can get delays per GEOM
>> provider, bandwidths, etc.
>
> Are you talking about C consumers or I can do that using Perl, Sh ?
>
> Is there any way to consume the metrics via Perl, for exa
> Anyway, for disk stats GEOM offers a nice API. You can get delays per GEOM
> provider, bandwidths, etc.
Are you talking about C consumers or I can do that using Perl, Sh ?
Is there any way to consume the metrics via Perl, for example ? I could not find
any decent documentation how to do that
On 9/23/14, 4:38 PM, Stefan Parvu wrote:
... I rather wish I could get the same information via sysctl. (Well,
something seems to be available via the "opaque" kern.devstat.all
sysctl(8) variable, but sysctl(8) doesn't display all of it, and parsing
it seems as if that would require knowledge ab
On Sep 23, 2014, at 10:38 AM, Stefan Parvu wrote:
>
>> ... I rather wish I could get the same information via sysctl. (Well,
>> something seems to be available via the "opaque" kern.devstat.all
>> sysctl(8) variable, but sysctl(8) doesn't display all of it, and parsing
>> it seems as if that wo
> ... I rather wish I could get the same information via sysctl. (Well,
> something seems to be available via the "opaque" kern.devstat.all
> sysctl(8) variable, but sysctl(8) doesn't display all of it, and parsing
> it seems as if that would require knowledge about the internals of the
> system
On Sep 22, 2014, at 11:22 PM, David Wolfskill wrote:
> ... I rather wish I could get the same information via sysctl. (Well,
> something seems to be available via the "opaque" kern.devstat.all
> sysctl(8) variable, but sysctl(8) doesn't display all of it, and parsing
> it seems as if that would
On 23/09/2014 00:22, David Wolfskill wrote:
> ... I rather wish I could get the same information via sysctl. (Well,
> something seems to be available via the "opaque" kern.devstat.all
> sysctl(8) variable, but sysctl(8) doesn't display all of it, and parsing
> it seems as if that would require kno
... I rather wish I could get the same information via sysctl. (Well,
something seems to be available via the "opaque" kern.devstat.all
sysctl(8) variable, but sysctl(8) doesn't display all of it, and parsing
it seems as if that would require knowledge about the internals of the
system where the d
12 matches
Mail list logo
