SAP HANA

The SAP HANA integration collects SAP HANA metrics and logs. The metrics are collected by querying relevant monitoring views. This integration writes structured trace logs.

For more information about HANA, see the SAP HANA documentation.

Prerequisites

To collect HANA telemetry, you must install the Ops Agent version 2.81.1 or higher.

This integration supports HANA version 2.0.

Configure your HANA instance

To collect metrics, a monitoring user requires SELECT access to the relevant monitoring views. The following SQL script creates a monitoring role and applies it to a monitoring user if executed by a user with sufficient permissions connected to the SAP HANA instance.

--Create the user
CREATE RESTRICTED USER otel_monitoring_user PASSWORD ;
--Enable user login
ALTER USER otel_monitoring_user ENABLE CLIENT CONNECT;
--Create the monitoring role
CREATE ROLE OTEL_MONITORING;
--Grant permissions to the relevant views
GRANT CATALOG READ TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_BACKUP_CATALOG TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_BLOCKED_TRANSACTIONS TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_CONNECTIONS TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_CS_ALL_COLUMNS TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_CS_TABLES TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_DATABASE TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_DISKS TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_HOST_RESOURCE_UTILIZATION TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_LICENSES TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_RS_TABLES TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_SERVICE_COMPONENT_MEMORY TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_SERVICE_MEMORY TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_SERVICE_REPLICATION TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_SERVICE_STATISTICS TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_SERVICE_THREADS TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_SERVICES TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_VOLUME_IO_TOTAL_STATISTICS TO OTEL_MONITORING;
GRANT SELECT ON SYS.M_WORKLOAD TO OTEL_MONITORING;
GRANT SELECT ON _SYS_STATISTICS.STATISTICS_CURRENT_ALERTS TO OTEL_MONITORING;
--Add the OTEL_MONITOR role to the monitoring user
GRANT OTEL_MONITORING TO otel_monitoring_user;

Configure the Ops Agent for HANA

Following the guide for Configuring the Ops Agent, add the required elements to collect telemetry from HANA instances, and restart the agent.

Example configuration

The following command creates the configuration to collect and ingest telemetry for HANA and restarts the Ops Agent.

# Configures Ops Agent to collect telemetry from the app and restart Ops Agent.

set -e

sudo tee /etc/google-cloud-ops-agent/config.yaml > /dev/null << EOF
logging:
  receivers:
    saphana:
      type: saphana
      include_paths:
      - /usr/sap/*/HDB*/saphanamon/trace/*.trc
      exclude_paths:
      - /usr/sap/*/HDB*/saphanamon/trace/nameserver_history*.trc
      - /usr/sap/*/HDB*/saphanamon/trace/nameserver*loads*.trc
      - /usr/sap/*/HDB*/saphanamon/trace/nameserver*executed_statements*.trc
  service:
    pipelines:
      saphana:
        receivers:
          - saphana
metrics:
  receivers:
    saphana:
      type: saphana
      username: SYSTEM
      password: G00g3l21
      endpoint: localhost:30015
  service:
    pipelines:
      saphana:
        receivers:
          - saphana
EOF

sudo service google-cloud-ops-agent restart

Configure logs collection

To ingest logs from HANA, you must create receivers for the logs that HANA produces and then create a pipeline for the new receivers.

To configure a receiver for your saphana logs, specify the following fields:

Field Default Description
exclude_paths [/usr/sap/*/HDB*/${HOSTNAME}/trace/nameserver_history*.trc, /usr/sap/*/HDB*/${HOSTNAME}/trace/nameserver*loads*.trc, /usr/sap/*/HDB*/${HOSTNAME}/trace/nameserver*executed_statements*.trc] A list of filesystem path patterns to exclude from the set matched by include_paths.
include_paths [/usr/sap/*/HDB*/${HOSTNAME}/trace/*.trc] A list of filesystem paths to read by tailing each file. A wild card (*) can be used in the paths.
record_log_file_path false If set to true, then the path to the specific file from which the log record was obtained appears in the output log entry as the value of the agent.googleapis.com/log_file_path label. When using a wildcard, only the path of the file from which the record was obtained is recorded.
type The value must be saphana.
wildcard_refresh_interval 60s The interval at which wildcard file paths in include_paths are refreshed. Given as a time duration, for example 30s or 2m. This property might be useful under high logging throughputs where log files are rotated faster than the default interval.

What is logged

The logName is derived from the receiver IDs specified in the configuration. Detailed fields inside the LogEntry are as follows.

The saphana logs contain the following fields in the LogEntry:

Field Type Description
jsonPayload.component string SAP HANA component
jsonPayload.thread_id number ID of the thread logging the message
jsonPayload.connection_id number ID of the connection where the message originated, if message was logged within the scope of a connection
jsonPayload.transaction_id number ID of the transaction where the message originated, if message was logged within the scope of a transaction
jsonPayload.update_transaction_id number ID of the update transaction where the message originated, if message was logged within the scope of an update transaction
jsonPayload.message string Log message
sourceLocation.file string Source file name
sourceLocation.line number Line within the source file

Configure metrics collection

To ingest metrics from HANA, you must create receivers for the metrics that HANA produces and then create a pipeline for the new receivers.

To configure a receiver for your saphana metrics, specify the following fields:

Field Default Description
ca_file Path to the CA certificate. As a client, this verifies the server certificate. If empty, the receiver uses the system root CA.
cert_file Path to the TLS certificate to use for mTLS-required connections.
collection_interval 60s A time.Duration value, such as 30s or 5m.
endpoint localhost:30015 The hostname:port used to connect to the saphana instance.
insecure true Sets whether or not to use a secure TLS connection. If set to false, then TLS is enabled.
insecure_skip_verify false Sets whether or not to skip verifying the certificate. If insecure is set to true, then the insecure_skip_verify value is not used.
key_file Path to the TLS key to use for mTLS-required connections.
password The password used to connect to the instance.
type This value must be saphana.
username The username used to connect to the instance.

What is monitored

The following table provides the list of metrics that the Ops Agent collects from the HANA instance.

Metric type 
Kind, Type
Monitored resources
Labels
workload.googleapis.com/saphana.alert.count
GAUGEINT64
gce_instance
rating
workload.googleapis.com/saphana.backup.latest
GAUGEINT64
gce_instance
 
workload.googleapis.com/saphana.column.memory.used
GAUGEINT64
gce_instance
host
subtype
type
workload.googleapis.com/saphana.component.memory.used
GAUGEINT64
gce_instance
component
host
workload.googleapis.com/saphana.connection.count
GAUGEINT64
gce_instance
host
status
workload.googleapis.com/saphana.cpu.used
CUMULATIVEINT64
gce_instance
host
type
workload.googleapis.com/saphana.disk.size.current
GAUGEINT64
gce_instance
host
path
state
usage_type
workload.googleapis.com/saphana.host.memory.current
GAUGEINT64
gce_instance
host
state
workload.googleapis.com/saphana.host.swap.current
GAUGEINT64
gce_instance
host
state
workload.googleapis.com/saphana.instance.code_size
GAUGEINT64
gce_instance
host
workload.googleapis.com/saphana.instance.memory.current
GAUGEINT64
gce_instance
host
state
workload.googleapis.com/saphana.instance.memory.shared.allocated
GAUGEINT64
gce_instance
host
workload.googleapis.com/saphana.instance.memory.used.peak
GAUGEINT64
gce_instance
host
workload.googleapis.com/saphana.license.expiration.time
GAUGEINT64
gce_instance
product
system
workload.googleapis.com/saphana.license.limit
GAUGEINT64
gce_instance
product
system
workload.googleapis.com/saphana.license.peak
GAUGEINT64
gce_instance
product
system
workload.googleapis.com/saphana.network.request.average_time
GAUGEDOUBLE
gce_instance
host
workload.googleapis.com/saphana.network.request.count
GAUGEINT64
gce_instance
host
state
workload.googleapis.com/saphana.network.request.finished.count
CUMULATIVEINT64
gce_instance
host
type
workload.googleapis.com/saphana.replication.average_time
GAUGEDOUBLE
gce_instance
mode
port
primary
secondary
workload.googleapis.com/saphana.replication.backlog.size
GAUGEINT64
gce_instance
mode
port
primary
secondary
workload.googleapis.com/saphana.replication.backlog.time
GAUGEINT64
gce_instance
mode
port
primary
secondary
workload.googleapis.com/saphana.row_store.memory.used
GAUGEINT64
gce_instance
host
type
workload.googleapis.com/saphana.schema.memory.used.current
GAUGEINT64
gce_instance
host
schema
type
workload.googleapis.com/saphana.schema.memory.used.max
GAUGEINT64
gce_instance
host
schema
workload.googleapis.com/saphana.schema.operation.count
CUMULATIVEINT64
gce_instance
host
schema
type
workload.googleapis.com/saphana.schema.record.compressed.count
GAUGEINT64
gce_instance
host
schema
workload.googleapis.com/saphana.schema.record.count
GAUGEINT64
gce_instance
host
schema
type
workload.googleapis.com/saphana.service.code_size
GAUGEINT64
gce_instance
host
service
workload.googleapis.com/saphana.service.count
GAUGEINT64
gce_instance
host
status
workload.googleapis.com/saphana.service.memory.compactors.allocated
GAUGEINT64
gce_instance
host
service
workload.googleapis.com/saphana.service.memory.compactors.freeable
GAUGEINT64
gce_instance
host
service
workload.googleapis.com/saphana.service.memory.effective_limit
GAUGEINT64
gce_instance
host
service
workload.googleapis.com/saphana.service.memory.heap.current
GAUGEINT64
gce_instance
host
service
state
workload.googleapis.com/saphana.service.memory.limit
GAUGEINT64
gce_instance
host
service
workload.googleapis.com/saphana.service.memory.shared.current
GAUGEINT64
gce_instance
host
service
state
workload.googleapis.com/saphana.service.memory.used
GAUGEINT64
gce_instance
host
service
type
workload.googleapis.com/saphana.service.stack_size
GAUGEINT64
gce_instance
host
service
workload.googleapis.com/saphana.service.thread.count
GAUGEINT64
gce_instance
host
status
workload.googleapis.com/saphana.transaction.blocked
GAUGEINT64
gce_instance
host
workload.googleapis.com/saphana.transaction.count
CUMULATIVEINT64
gce_instance
host
type
workload.googleapis.com/saphana.volume.operation.count
CUMULATIVEINT64
gce_instance
host
path
type
usage_type
workload.googleapis.com/saphana.volume.operation.size
CUMULATIVEINT64
gce_instance
host
path
type
usage_type
workload.googleapis.com/saphana.volume.operation.time
CUMULATIVEINT64
gce_instance
host
path
type
usage_type

Sample dashboard

To view your HANA metrics, you must have a chart or dashboard configured. Cloud Monitoring provides a library of sample dashboards for integrations, which contain preconfigured charts. For information about installing these dashboards, see Installing sample dashboards.

Verify the configuration

This section describes how to verify that you correctly configured the HANA receiver. It might take one or two minutes for the Ops Agent to begin collecting telemetry.

To verify that the logs are ingested, go to the Logs Explorer and run the following query to view the HANA logs:

resource.type="gce_instance"
log_id("saphana")

To verify that the metrics are ingested, go to Metrics Explorer and run the following query in the MQL tab:

fetch gce_instance
| metric 'workload.googleapis.com/saphana.connection.count'
| every 1m

What's next

For a walkthrough on how to use Ansible to install the Ops Agent, configure a third-party application, and install a sample dashboard, see the Install the Ops Agent to troubleshoot third-party applications video.