Closed VihasMakwana closed 4 months ago
@VihasMakwana once this is implemented I believe it will work right away without any more changes required on the Beats side thanks to https://github.com/elastic/beats/pull/40025#pullrequestreview-2178406475 right?
@VihasMakwana once this is implemented I believe it will work right away without any more changes required on the Beats side thanks to https://github.com/elastic/beats/pull/40025#pullrequestreview-2178406475 right?
We will need a small tweak here https://github.com/elastic/beats/blob/c00345ffc1cfea63f1ff46e6af981e0a0a19adf0/metricbeat/module/system/process/process.go#L113-L116 Apart from this, nothing else is required.
Well I guess we will have to create a new release of the elastic-agent-system-metrics but that was already part of the plan.
While monitoring set of processes, we don't return them to the caller but rather log them at debug leve.
Example of such logs are:
Such logs captures important information such as "permission denied", "partial metrics" etc.
With the recent introduction of the status reporter for
metricsets
, it is impossible to change the status to degraded if such errors are not passed to the caller.Proposed Solution
mutierr
to combine the important errors and pass it to caller with the metrics and let the caller decide what to do.Please share your thoughts on this!
cc: @cmacknz @pierrehilbert @jlind23