Sysctl as a Service, or: making sysctl(3) more friendly for monitoring systems

[Steven Hartland]

Gathering every sysctl would case issues as some are very heavy and if 
called regularly would cause noticeable stalls.

On 13/12/2016 16:16, Mark Rushakoff wrote:
> In Prometheus' node_exporter, it looks like they're calling sysctl to grab
> just
> CPU or just memory, etc., metrics.
>
> On the InfluxDB side of things, I'm not seeing any Telegraf plugin to
> monitor
> sysctl in a generic way, although you could probably emit InfluxDB line
> protocol pretty easily from the exporter tool or something similar to that.
>
> My impression, from a monitoring perspective, is that there isn't much
> demand
> to gather _everything_ in sysctl in a single call, although categorized
> subsets
> might be appealing.
>
>
> On Mon, Dec 12, 2016 at 5:34 AM, Ed Schouten <ed at nuxi.nl> wrote:
>
>> Hi Jonathan,
>>
>> 2016-12-11 21:12 GMT+01:00 Jonathan Anderson <jonathan at freebsd.org>:
>>> Rather than doing lots of system calls to
>>> enumerate clearly-related sysctl values, it would be very cool to do one
>>> system call and then inspect the resulting data structure in memory.
>> I'm not sure it's worth tackling this problem at this time. My current
>> version of the exporter is already pretty fast:
>>
>> $ time ./prometheus_sysctl_exporter | wc -l
>>          0.00 real         0.00 user         0.00 sys
>>      3162
>>
>> If our sysctl tree would get substantially larger at some point, we
>> should of course revisit this.
>>
>> --
>> Ed Schouten <ed at nuxi.nl>
>> Nuxi, 's-Hertogenbosch, the Netherlands
>> KvK-nr.: 62051717
>> _______________________________________________
>> freebsd-hackers at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
>>
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"