Skip to main content
Version: 76.0.0

Resource Considerations

This document describes resource considerations and limitations to be taken into account when provisioning and operating a9s Prometheus Service Instances.

The resource requirements of a Service Instance depend on the Template selected for its Service Plan. Each Template defines the topology (number of nodes) and the set of colocated processes. Templates that provide logging require a higher-memory VM type and more ephemeral disk than Templates without logging.

The Platform Operator must define matching vm_type and persistent_disk_type entries in the BOSH Cloud Config and reference them from the Service Plan configuration. For guidance on Service Plans and Templates, see Service Plans and Available Templates.

For guidance on Service Plans and Templates, see Service Plans and Available Templates.

Template Requirements

The resource requirements of a Service Instance depend on the Template selected for its Service Plan. The small, medium, and large labels used for VM type and persistent disk type in the tables below refer to the example Cloud Config entries defined in Update the Cloud Config.

The following table lists resource requirements per VM, as well as totals across all nodes of a Service Instance.

Template nameVM RoleNodesvCPUsLoggingMin. RAMMin. Persistent DiskMin. Ephemeral DiskExample VM TypeExample Persistent Disk Type
prometheus2-grafana10-singlePrometheus12No4 GB4 GB5 GBsmallsmall
Grafana12No4 GB4 GB5 GBsmallsmall
Alertmanager12No4 GB4 GB5 GBsmallsmall
prometheus3-grafana13-singlePrometheus12No4 GB4 GB5 GBsmallsmall
Grafana12No4 GB4 GB5 GBsmallsmall
Alertmanager12No4 GB4 GB5 GBsmallsmall
Retention Period Drives Disk Usage

The Prometheus VM stores time-series metrics on persistent disk using the Prometheus Time Series Database; disk usage grows linearly with scrape interval, metric cardinality, and retention period. The default retention period is 15 days. The small disk type (4 GB) is a minimum starting point for the Prometheus VM; disk sizing must be revisited whenever the retention period or the set of scrape targets changes.