Note: Sysdig follows the Prometheus-compabtible naming convention for both metrics and labels as opposed to the previous statsd-compatible, legacy Sysdig naming convention. However, this page still shows metrics in the legacy Sysdig naming convention. Until this page is updated, see Metrics and Label Mapping for the mapping between Sysdig legacy and Prometheus naming conventions.
dragent is the main process in the agent that collects and collates
data from multiple sources, including syscall events from the kernel in
order to generate metrics. The
analyzer module that runs in the
dragent process does much of the work involved in generating metrics.
These internal metrics are used to troubleshoot the health of the
Sysdig Monitor provides the following analyzer metrics:
|Minimum Agent Version
|0.80.0 or above
|The number of processes found by the analyzer.
|The number of threads found by the analyzer.
|The number of threads not reported due to thread limits.
|The number of containers found by the analyzer.
|The number of java processes found by the analyzer.
|The number of application checks reporting to the analyzer.
|If the agent is configured to autodetect a Mesos environment, value is 1, otherwise is 0.
|If the agent actually found a Mesos environment, value is 1, otherwise, value is 0
|The analyzer flush CPU % (0-100)
|The analyzer flush duration (milliseconds)
|The current sampling ratio (1=all events, 2= half of events analyzed, 4=one fourth of events analyzed, and so on.
|The number of events processed
|The number of events dropped
|The number of events dropped due to the buffer being full.
|The number of driver preemptions.
|The number of command lines collected and sent to the collector.
|0.80.1 or above
|The number of command lines identified as container health checks. This metric does not change even if healthcheck command lines are not sent to the collector.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.