Monitoring PAS

This guide describes how Pivotal Cloud Foundry (PCF) operators can monitor their Pivotal Application Service (PAS) deployments. For information about monitoring Pivotal Container Service (PKS) deployments, see Logging and Monitoring PKS.

For more information about logging and metrics in PCF, see Overview of Logging and Metrics.


This guide includes the following topics:

  • Key Performance Indicators: A list of Key Performance Indicators (KPIs) that operators may want to monitor with their PAS deployment to help ensure it is in a good operational state.
  • Key Capacity Scaling Indicators: A list of capacity scaling indicators that operators may want to monitor to determine when they need to scale their PAS deployments.
  • Selecting and Configuring a Monitoring System: Guidance for setting up PAS with monitoring platforms to continuously monitor component metrics and trigger health alerts.

KPI Changes from PAS v2.3 to v2.4

This table highlights new and changed KPIs in PAS v2.4.

Modified KPI: locket.ActiveLocks

The Clock Global (Cloud Controller clock) job now also holds a component lock. Therefore the expected number of Active Locks increased to 5. If the Operator disables Zero Downtime App Deployments when configuring PAS, then the expected value will remain 4 for PAS v2.4.
New KPI: doppler_proxy.slow_consumer

This metric indicates that a Firehose consumer, such as a monitoring tool nozzle, is ingesting messages from the Firehose too slowly.
New KPI: rlp.dropped, direction: egress

This metric indicates that a Reverse Log Proxy (RLP) consumer, such as a monitoring tool nozzle, is ingesting RLP messages too slowly.

Monitor PCF Services

For information about KPIs and metrics for PCF services, see the following topics:

Create a pull request or raise an issue on the source for this page in GitHub