Set Up the Environment
If you are already leveraging Kubernetes Service Discovery, specifically the approach given in prometheus-kubernetes.yml, you might already have annotations attached to the pods that mark them as eligible for scraping. Such environments can quickly begin scraping the same metrics by using the Sysdig agent in a single step.
If you are not using Kubernetes Service Discovery, follow the instructions given below:
Ensure that the Kubernetes pods that contain your Prometheus exporters have been deployed with the following annotations to enable scraping, substituting the listening
spec: template: metadata: annotations: prometheus.io/scrape: "true" prometheus.io/port: "exporter-TCP-port"
The configuration above assumes your exporters use the typical endpoint called
/metrics. If your exporter is using a different
endpoint, specify by adding the following additional annotation, substituting the
Use the Sample Exporter to test your environment. You will quickly see auto-discovered Prometheus metrics being displayed on Sysdig Monitor. You can use this working example as a basis to similarly annotate your own exporters.
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.