Collect Prometheus Metrics
Sysdig supports collecting, storing, and querying Prometheus native metrics and labels. You can use Sysdig in the same way that you use Prometheus and leverage Prometheus Query Language (PromQL) to create dashboards and alerts. Sysdig is compatible with Prometheus HTTP API to query your monitoring data programmatically using PromQL and extend Sysdig to other platforms like Grafana.
From a metric collection standpoint, a lightweight Prometheus server is directly embedded into the Sysdig agent to facilitate metric collection. This also supports targets, instances, and jobs with filtering and relabeling using Prometheus syntax. You can configure the agent to identify these processes that expose Prometheus metric endpoints on its own host and send it to the Sysdig collector for storing and further processing.
The Prometheus product itself does not necessarily have to be installed for Prometheus metrics collection.
See the Sysdig agent versions and compatibility with Prometheus features:
Sysdig Agent v12.2.0 and Above
The following features are enabled by default:
- Automatically scraping any Kubernetes pods with the following annotation set:
- Automatically scrape applications supported by Monitoring Integrations.
For more information, see Set up the Environment.
Sysdig Agent Prior to v12.0.0
Manually enable Prometheus in
prometheus: enabled: true
For more information, see Enable Promscrape V2 on Older Versions of Sysdig Agent .
The following topics describe in detail about setting up the environment for service discovery, metrics collection, and further processing.
See the following blog posts for additional context on the Prometheus metric and how such metrics are typically used.
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.