You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Investigating the situation with atop shows, that lsb_release is called on every collection interval (10s by default), firing up a python interpreter each time.
Reading the docs for input.system I ask myself, why it is actually calling lsb_release? input.system reads load, uptime, #cpus and #users, I don't get the point for running lsb_release?
I would be nice to have this removed or at least to add an option to be able to turn this off.
The text was updated successfully, but these errors were encountered:
Good catch, looks like it's from gopsutil, the library we are using to gather metrics. The only data we are using from that call, however, is the system uptime, which they have a more efficient means of gathering.
Relevant telegraf.conf:
[[inputs.system]]
System info:
Steps to reproduce:
Expected behavior:
cpu usage <5%
Actual behavior:
cpu usage ~25% caused by telegraf
Additional info:
Investigating the situation with
atop
shows, thatlsb_release
is called on every collection interval (10s by default), firing up a python interpreter each time.Reading the docs for input.system I ask myself, why it is actually calling
lsb_release
? input.system reads load, uptime, #cpus and #users, I don't get the point for runninglsb_release
?I would be nice to have this removed or at least to add an option to be able to turn this off.
The text was updated successfully, but these errors were encountered: