Skip to content

Latest commit

 

History

History
693 lines (388 loc) · 14.3 KB

view-monitoring-metrics-of-a-database-system-b02814d.md

File metadata and controls

693 lines (388 loc) · 14.3 KB

View Monitoring Metrics of a Database System

In the cockpit, you can view the current metrics of a selected database system to get information about its health state. You can also view the metrics history of a productive database to examine the performance trends of your database over different intervals of time or investigate the reasons that have led to problems with it. You can view the metrics for all types of databases.

The readMonitoringData scope is assigned to the used platform role for the subaccount. For more information, see Platform Scopes.

Context

Remember:

SAP Business Technology Platform, Neo environment will sunset on December 31, 2028, subject to terms of customer or partner contracts.

For more information, see SAP Note 3351844.

Tip:

This documentation refers to SAP Business Technology Platform, Neo environment. If you are looking for documentation about other environments, see SAP Business Technology Platform ↗️.

Note:

You can also retrieve the current metrics of a database system with the Metrics API.

Default Metrics of a Database System

Metric

Value

Execution Frequency

CPU Load

The percentage of the CPU that is used on average over the last minute.

This metric is updated every minute.

An alert is triggered when 2 consecutive checks with an interval of 1 minute aren’t in an OK state.

Disk I/O

The number of bytes per second that are currently being read or written to the disc. from the navigation area or from the

This metric is updated every minute.

An alert is triggered when 5 consecutive checks with an interval of 1 minute aren’t in an OK state.

Network Ping

The percentage of packets that are lost to the database host.

This metric is updated every minute.

An alert is triggered when 2 consecutive checks with an interval of 1 minute aren’t in an OK state.

OS Memory Usage

from the navigation area or from theThe percentage of the operating system memory that is currently being used.

This metric is updated every minute.

An alert is triggered when 2 consecutive checks with an interval of 1 minute aren’t in an OK state.

Used Disc Space

The percentage of the local discs of the operating system that is currently being used.

Note:

If this metric is in a critical state, try restarting the database system. If the restart doesn’t work, check the troubleshooting documentation. See the Related Information section.

This metric is updated every minute.

An alert is triggered when 5 consecutive checks with an interval of 1 minute aren’t in an OK state.

Default Metrics of an SAP HANA System

Metric

Value

Execution Frequency

HANA DB Availability

  • OK - the database is reachable from our central admin component via JDBC.

  • Critical - either the database is down or overloaded, or there's a network issue.

This metric is updated every minute.

An alert is triggered when 3 consecutive checks with an interval of 1 minute aren’t in an OK state.

HANA DB Alerting Availability

  • OK - alerts can be retrieved from the SAP HANA system.

  • Critical - alerts can’t be retrieved as there’s no connection to the database. This also implies that any other visible metric may be outdated.

This metric depends on the HANA DB Availability metric.

This metric is updated every minute.

An alert is triggered when 3 consecutive checks with an interval of 1 minute aren’t in an OK state.

HANA DB Compile Server

  • OK - the compiler server is running on the SAP HANA system.

  • Critical - the compile server crashed or was otherwise stopped. The service should recover automatically. If this doesn’t work, a restart of the system might be necessary.

This metric is updated every 10 minutes.

An alert is triggered when 3 consecutive checks with an interval of 1 minute aren’t in an OK state.

HANA DB Backup Volumes Availability

  • OK - the backup volumes are available.

  • Critical - the backup volumes aren’t available.

This metric is updated every 15 minutes.

An alert is triggered when 3 consecutive checks with an interval of 1 minute aren’t in an OK state.

HANA DB Data Backup Age

  • OK - the age of the last data backup is below the critical threshold.

  • Critical - the age of the last data backup is above the critical threshold.

This metric is updated every 24 hours.

An alert is triggered when 3 consecutive checks with an interval of 1 minute aren’t in an OK state.

HANA DB Data Backup Exists

  • OK - the data backup exists.

  • Critical - no data backup exists.

This metric is updated every 24 hours.

An alert is triggered when 3 consecutive checks with an interval of 1 minute aren’t in an OK state.

HANA DB Data Backup Successful

  • OK - the last data backup was successful.

  • Critical - the last data backup wasn’t successful.

This metric is updated every 24 hours.

An alert is triggered when 3 consecutive checks with an interval of 1 minute aren’t in an OK state.

HANA DB Log Backup Successful

  • OK - the last log backup was successful.

  • Critical - the last log backup failed.

This metric is updated every 10 minutes.

An alert is triggered when 3 consecutive checks with an interval of 1 minute aren’t in an OK state.

HANA DB Service Memory Usage

  • OK - no server is running out of memory.

  • Critical - a service is causing an out of memory error. See SAP Note 1900257.

This metric is updated every 5 minutes.

An alert is triggered when 3 consecutive checks with an interval of 1 minute aren’t in an OK state.

HANA XS Availability

  • OK - XSEngine accepts HTTPS connections.

  • Critical - XSEngine doesn’t accept HTTPS connections.

This metric is updated every minute.

An alert is triggered when 3 consecutive checks with an interval of 1 minute aren’t in an OK state.

HANA Dump Files Count

  • OK - Up to 10 dump files exist.

  • Warning - More than 10 dump files exist.

  • Critical - More than 20 dump files exist. Try to analyze the dump files.

Note:

If you’re still having issues, check the troubleshooting documentation. See the Related Information section.

The metric is updated every hour.

An alert is triggered when a check isn't in an OK state.

HANA Tenant Databases Unused Memory

  • OK - More than 10% of the total free memory is available to the tenant databases, including fragmented memory. Nameserver reservation is excluded.

  • Warning - 10% or less of the total free memory can be used by the tenant databases.

  • Critical - 2% or less of the total free memory can be used by the tenant databases.

The metric is updated every hour.

Default Metrics of an SAP ASE System

Metric

Value

Execution Frequency

Sybase ASE Availability

  • OK - the database is reachable from our central admin component via JDBC.

  • Critical - either the database is down or overloaded, or there's a network issue.

This metric is updated every minute.

An alert is triggered when 3 consecutive checks with an interval of 1 minute aren’t in an OK state.

Sybase ASE Long Running Trans

  • OK - a transaction is running for up to an hour.

  • Warning - a transaction is running for more than an hour.

  • Critical - a transaction is running for more than 13 hours.

This metric is updated every 2 minutes.

An alert is triggered when a consecutive check with an interval of 1 minute isn’t in an OK state.

Sybase ASE HADR Fm State

FaultManager is a component for highly available (HA) SAP ASE systems that triggers a failover in case the primary node isn’t working.

  • OK - FaultManager for a system that is set up as an HA system is running properly.

  • Critical - FaultManager isn’t working properly and the failover doesn’t work.

This metric is updated every 2 minutes.

An alert is triggered when a consecutive check with an interval of 1 minute isn’t in an OK state.

Sybase ASE HADR Latency

  • OK - the latency for the HA replication path is less than or equal to 10 minutes.

  • Warning - the latency is greater than 10 minutes.

  • Critical - the latency is greater than 20 minutes. A high latency might lead to data loss if there’s a failover.

This metric is updated every 2 minutes.

An alert is triggered when a consecutive check with an interval of 1 minute isn’t in an OK state.

Sybase ASE HADR Primary State

  • OK - the primary host of a system that is set up as HA system is running fine.

  • Critical - the primary host isn’t running properly.

This metric is updated every 2 minutes.

An alert is triggered when a consecutive check with an interval of 1 minute isn’t in an OK state.

Sybase ASE HADR Standby State

  • OK - the secondary or standby host of a system that is set up as HA system is running properly.

  • Critical - the secondary or standby host isn’t running properly.

This metric is updated every 2 minutes.

An alert is triggered when a consecutive check with an interval of 1 minute isn’t in an OK state.

Sybase ASE Procedure Cache Usage

  • OK - procedure cache usage is below 80%.

  • Warning - procedure cache usage is more than 80% but less than 89%.

  • Critical - procedure cache usage is more than 90%.

This metric is updated every 2 minutes. An alert is is triggered when a consecutive check with an interval of 1 minute isn't in an OK state.

Procedure

  1. Open the subaccount in the SAP BTP cockpit.

  2. Navigate to the Database Systems page either by choosing SAP HANA / SAP ASE > Database Systems**Overview page.

    All database systems available in the selected subaccount are listed with their details, including the database version and state, and the number of associated databases.

  3. Choose the entry for the relevant database system in the list.

  4. Choose Monitoring from the navigation area to get detailed information about the current state and the history of metrics for the selected database system.

    When you open the checks history, you can view graphic representations for each of the different checks, and zoom in to see additional details. If you zoom in a graphic horizontally, all other graphics also zoom in to the same level of detail. Press [Shift] and drag to pan a graphic. Zoom out to the initial size by double-clicking.

    You can select different periods for each check. Depending on the interval you select, data is aggregated as follows:

    • Last 12 or 24 hours - data is collected every minute.
    • Last 7 days - data is aggregated from the average values for each 10 minutes.
    • Last 30 days - data is aggregated from the average values for each hour.

    You can also select a custom time interval for viewing check history.

Related Information

SAP BTP Cockpit

Metrics REST API for Database Systems ↗️