Monitoring PAS

This guide describes how Pivotal Platform 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 Pivotal Platform, see Overview of Logging and Metrics.

KPI and Scaling Changes from PAS v2.6 to v2.7

This table highlights new and changed KPIs and scaling indicators in PAS v2.7.

Status Metric Description Reference
Removed Number of Route Registration Messages Sent and Received The gorouter.registry_message.route-emitter and route_emitter.HTTPRouteNATSMessagesEmitted metrics are no longer an accurate representation of routing health.

In PAS v2.4 and later, Gorouter skips the TTL for routes that are registered with TLS. This means the routes never expire or get pruned, other than in an attempt to connect to an invalid backend.
N/A
Removed Adapter Loss Rate The Adapter Loss Rate metric is replaced by Syslog Agent Loss Rate. In PAS v2.7, Syslog Adapters are removed from the Loggregator architecture. Syslog Agents replace Syslog Adapters.

For more information about Syslog Agents, see Agent-Based Syslog Egress Is Enabled by Default in Pivotal Application Service v2.7 Release Notes.
Syslog Agent Loss Rate
Removed CF Syslog Drain Bindings Count In PAS v2.6 and earlier, CF syslog drain bindings were required to manage connections between the Syslog Adapters and the Reverse Log Proxies (RLPs).

In PAS v2.7, Syslog Agents replace Syslog Adapters. Syslog Agents do not use CF syslog drain bindings to manage syslog drains.

For more information about Syslog Agents, see Agent-Based Syslog Egress Is Enabled by Default in Pivotal Application Service v2.7 Release Notes.
N/A

Monitor Pivotal Platform Services

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