Monitoring Architecture: SAP HANA Cockpit 2.0, Alert Management & Metrics
A complete architectural guide to SAP HANA monitoring using SAP HANA Cockpit 2.0, Cockpit Manager, internal Statistics Server alert evaluation, and real-time operational thresholds for CPU, Memory, Disk, and Replication.
IntermediateMonitoring~16 min studyHANA 2.0 SPS 02 - SPS 07+
Core Learning Objectives
- 1.Understand SAP HANA Cockpit 2.0 architecture and resource group governance.
- 2.Contrast SAP HANA Cockpit against legacy SAP HANA Studio.
- 3.Configure and interpret the SAP HANA Statistics Service alerting framework.
- 4.Query alert history and configure email notification thresholds.
Prerequisites:hana-architecture-services-overviewhana-fundamentals-overview
Definition & Architectural Rationale
Technical Definition:
SAP HANA Cockpit 2.0 is the official browser-based administration and monitoring console for SAP HANA landscapes, providing unified performance management, security administration, database health cards, and automated alerting.
Why this component exists:
SAP HANA Studio was an Eclipse-based client tool requiring desktop installation and lacked centralized multi-database management. Cockpit 2.0 is a centralized web application running on XS Advanced (XSA) that manages hundreds of production and non-production HANA databases through a single interface.
Internal Working & Mechanics
1. Cockpit 2.0 Architecture:
- Built on SAP HANA XS Advanced (XSA) runtime with a dedicated backend database (cockpit-db).
- Cockpit Manager: Web UI for user provisioning, registering resource groups, and granting database administrator privileges.
- Resource Directory: Contains connection endpoints, technical user credentials (stored securely), and SSL certificates for target HANA databases.
2. Embedded Statistics Service (ESS):
- In older versions (HANA 1.0), the statistics service was a standalone process (hdbstatisticsserver).
- In HANA 2.0, the Statistics Service is embedded directly inside the master Name Server (SystemDB) and Index Server (Tenant) to eliminate inter-process communication latency.
- ESS executes periodic SQL queries against internal M_* views every 1 to 15 minutes, comparing metrics against threshold rules defined in the _SYS_STATISTICS schema.
- When a threshold is breached (e.g. Memory > 90%, Log Disk > 90%, Backup age > 24 hours), ESS writes an alert entry to _SYS_STATISTICS.STATISTICS_CURRENT_ALERTS and triggers alert emails.
Architecture Flow Diagram
Mermaid DiagramMonitoring Architecture: SAP HANA Cockpit 2.0, Alert Management & Metrics
Architectural Flow: Cockpit 2.0 connects via JDBC/SSL to managed databases. Each database evaluates internal metrics through its Embedded Statistics Service and reports active alerts back to the Cockpit dashboard.
Production SQL Diagnostics
Query Active High and Medium System Alerts (_SYS_STATISTICS)Safe (Read-Only)
Retrieves all open database alerts evaluated by the Embedded Statistics Service.
Both
Privileges: MONITORING or CATALOG READ
Target Engine: HANA 2.0 (All SPS)
SELECT
ALERT_RATING AS SEVERITY,
ALERT_NAME,
ALERT_DETAILS,
ROUND(SECONDS_BETWEEN(SNAPSHOT_TIME, CURRENT_UTCTIMESTAMP) / 60, 1) AS AGE_MINUTES,
SNAPSHOT_TIME
FROM _SYS_STATISTICS.STATISTICS_CURRENT_ALERTS
WHERE ALERT_RATING >= 2 -- 2 = Low, 3 = Medium, 4 = High
ORDER BY ALERT_RATING DESC, SNAPSHOT_TIME DESC;
Key Diagnostic Columns
SEVERITY:4 = High (Critical), 3 = Medium (Warning), 2 = LowALERT_NAME:Specific alert ID (e.g. Check disk space, Check full backup age)ALERT_DETAILS:Human-readable explanation of threshold breachExpected Diagnostic Output
SEVERITY | ALERT_NAME | ALERT_DETAILS | AGE_MINUTES | SNAPSHOT_TIME --------------------------------------------------------------------------------------------------------------------- 4 | Check disk space | Disk volume /hana/log is 92% full (exceeds threshold 90%). | 4.2 | 2026-10-23 08:25:00 3 | Expensive statement check | 5 statements took longer than 60 seconds in the last 15 mins. | 12.0 | 2026-10-23 08:18:00
DBA Interpretation: Critical severity 4 alert: /hana/log has breached 90% capacity and requires immediate DBA remediation before log freeze.
Troubleshooting & Root Cause Analysis
Production Best Practices & Operational Risks
Mandatory Best Practices
- Configure email alert notifications in SAP HANA Cockpit for all Severity 4 (High) alerts to notify the on-call DBA immediately.
- Audit the Embedded Statistics Service execution frequency to ensure it does not schedule heavy diagnostic queries during peak business hours.