has anyone ever seen their osqueryd have high peak...
# kolide
a
has anyone ever seen their osqueryd have high peaks in CPU usage? I’m curious how someone would resolve query execution randomly pegging CPU usage every 10 seconds between when the agent talks to /api/v1/osquery/distributed/read and when it hits /api/v1/osquery/log
z
Do you see anything in the osquery status logs? Could there be a label query that is CPU expensive? Can you see any outliers in
select * from osquery_schedule
?