Prometheus
Prometheus is a monitoring platform that collects metrics from targets by scraping their published endpoints.
Prisma Cloud can be configured to be a Prometheus target.
You can use Prometheus to monitor time series data across your environment and show high-level, dashboard-like, stats to visualize trends and changes.
Prisma Cloud’s instrumentation lets you track metrics such as the total number of connected Defenders and the total number of container images in your environment being protected by Defender.
Metrics
Metrics are a core Prometheus concept.
Instrumented systems expose metrics.
Prometheus stores the metrics in its time-series database, and makes them easily available to query to understand how systems behave over time.
Prisma Cloud has two types of metrics:
- Counters: Single monotonically increasing values. A counter’s value can only increase or be reset to zero.
- Gauges: Single numerical values that can arbitrarily go up or down.
Prisma Cloud metrics
All Prisma Cloud metrics are listed in the following table.
Vulnerability and compliance metrics are updated every 24 hours.
The rest of the metrics are updated every 10 minutes.
Note that *_vulnerabilities and *_compliance metrics report how many entities (images, containers, hosts, etc) are at risk by the highest severity issue that impacts them.
In other words, images_critical_vulnerabilities is not a total count of critical vulnerabilities in the images in your environment.
Rather, it is a total count of images where the highest severity CVE is critical.
For a thorough explanation of how this type of metric is used, see Vulnerability Explorer.
Metric | Type | Description |
|---|---|---|
totalDefenders | Gauge | Total number of Defenders connected to Console.
Connected and disconnected Defenders can be reviewed in Console under Manage > Defenders > Manage . |
activeDefenders | Gauge | Total number of all Defenders for which a license is allocated, regardless of whether it is currently connected to Console or not. |
images_critical_vulnerabilities | Gauge | Total number of containers impacted by critical vulnerabilities. |
images_high_vulnerabilities | Gauge | Total number of containers impacted by high vulnerabilities. |
images_medium_vulnerabilities | Gauge | Total number of containers impacted by medium vulnerabilities. |
images_low_vulnerabilities | Gauge | Total number of containers impacted by low vulnerabilities. |
hosts_critical_vulnerabilities | Gauge | Total number of hosts impacted by critical vulnerabilities. |
hosts_high_vulnerabilities | Gauge | Total number of hosts impacted by high vulnerabilities. |
hosts_medium_vulnerabilities | Gauge | Total number of hosts impacted by medium vulnerabilities. |
hosts_low_vulnerabilities | Gauge | Total number of hosts impacted by low vulnerabilities. |
serverless_critical_vulnerabilities | Gauge | Total number of serverless functions impacted by critical vulnerabilities. |
serverless_high_vulnerabilities | Gauge | Total number of serverless functions impacted by high vulnerabilities. |
serverless_medium_vulnerabilities | Gauge | Total number of serverless functions impacted by medium vulnerabilities. |
serverless_low_vulnerabilities | Gauge | Total number of serverless functions impacted by low vulnerabilities. |
images_critical_compliance | Gauge | Total number of images impacted by critical compliance issues. |
images_high_compliance | Gauge | Total number of images impacted by high compliance issues. |
images_medium_compliance | Gauge | Total number of images impacted by medium compliance issues. |
images_low_compliance | Gauge | Total number of images impacted by low compliance issues. |
containers_critical_compliance | Gauge | Total number of containers impacted by critical compliance issues. |
containers_high_compliance | Gauge | Total number of containers impacted by high compliance issues. |
containers_medium_compliance | Gauge | Total number of containers impacted by medium compliance issues. |
containers_low_compliance | Gauge | Total number of containers impacted by low compliance issues. |
hosts_critical_compliance | Gauge | Total number of hosts impacted by critical compliance issues. |
hosts_high_compliance | Gauge | Total number of hosts impacted by high compliance issues. |
hosts_medium_compliance | Gauge | Total number of hosts impacted by medium compliance issues. |
hosts_low_compliance | Gauge | Total number of hosts impacted by low compliance issues. |
serverless_critical_compliance | Gauge | Total number of serverless functions impacted by critical compliance issues. |
serverless_high_compliance | Gauge | Total number of serverless functions impacted by high compliance issues. |
serverless_medium_compliance | Gauge | Total number of serverless functions impacted by medium compliance issues. |
serverless_low_compliance | Gauge | Total number of serverless functions impacted by low compliance issues. |
active_app_firewalls | Gauge | Total number of active app firewalls (WAAS). |
app_firewall_events | Gauge | Total number of app firewall (WAAS) events. |
protected_containers | Gauge | Total number of protected containers. |
container_runtime_events | Gauge | Total number of container runtime events. |
host_runtime_events | Gauge | Total number of host runtime events. |
access_events | Gauge | Total number of access events. |
api_requests | Counter | Total number of requests to the Prisma Cloud API. |
defender_events | Counter | Total number of events sent by all Defenders to Console. |
Integrating Prisma Cloud with Prometheus
The Prometheus server scrapes endpoints at configurable time intervals.
Prisma Cloud refreshes vulnerability and compliance data every 24 hours.
All other data is refreshed every 10 minutes.
Regardless of the value you set for the Prometheus scrape interval, new Prisma Cloud data is only available at our refresh rates.
This procedure shows you how to enable Prisma Cloud’s Prometheus integration and spin up a Prometheus server running in a container.
If you already have a Prometheus server in your environment, all you need is the Prisma Cloud scrape configuration.
- Enable Prisma Cloud’s Prometheus instrumentation.
- Log into Prisma Cloud Console.
- Go toManage > Alerts > Logging.
- SetPrometheus instrumentationtoEnabled.
- Prepare a scrape configuration file for the Prometheus server.
- Create a new file named prometheus.yml, and open it for editing.
- Enter the following configuration, where:
- CONSOLE_ADDRESS is the DNS name or IP address for Prisma Cloud Console.
- USER is a Prisma Cloud user, with the minimum role of Auditor.
- PASS is the user’