Retrieves RUM metrics from SAP Cloud ALM API. Publishes time-series metrics and evaluates alarms per configured rule.

• API: GET /api/calm-metrics/v1/metrics?provider=rum

Requires a Web Service connector with authentication type CLOUD_ALM.

SAP Cloud ALM Connector

Based on a service key from the SAP Cloud ALM API service instance in the BTP subaccount.

Required OAuth scopes in the authorities list of the instance parameters:

• $XSMASTERAPPNAME.calm-api.hm.read
• $XSMASTERAPPNAME.calm-api.metrics.read
• $XSMASTERAPPNAME.calm-api.rum.personal.read (optional) needed to see real user names. Without it user names appear anonymized.

• Publishes six metric types per RUM datapoint: responseTime users requests okStatus warningStatus criticalStatus
• Per-row thresholds with standard G2W:80 W2M:90 syntax. Multi Threshold Syntax
• Attributes Filter narrows which datapoints a row evaluates
• Exclusive controls whether a matched datapoint is consumed or passed to later rows
• Glob support for Metric and Service name fields (* = all; note: partial globs like *Status do NOT work on Metric)
• Optional alarm tag for grouping or routing
• Auto-clear when alarm condition no longer matches
• Load Services button: auto-discovers RUM service IDs and labels from the live tenant and populates Service name and Service ID in the table

Data collection populates Service name and Service ID from the Cloud ALM landscape. It calls the RUM analytics filters API to resolve the exact service labels used by the metrics API (e.g. S4H.100 not S4H).

Always run data collection before adding rows. A service name not returned by data collection will not match what the metrics API returns and the row will never apply.

Data collection runs two calls:

1. POST /api/calm-analytics/v1/analytics/providers/filters with body {“providerName”:“DP_RUM_REQUEST_TYPES”,“providerVersion”:“v1”} — returns the RUM service filter list. Extracts each service UUID and its label (e.g. S4H.100).
2. GET /api/calm-landscape/v1/landscapeObjects — returns all landscape objects. Each object is checked against the RUM map. If found the RUM label is used as Service name. If not found the landscape name is used as fallback.

If the first call fails data collection falls back to showing all landscape objects without RUM label resolution.

Why the label matters: the metrics API returns service.name = S4H.100. The landscape object name is S4H. Without label resolution S4H* would fail to match S4H.100 and no rows would apply.

Click Load Services to run data collection and populate the surveillance table.

1. Open monitor configuration
2. Click Load Services
3. Table populates with Service name and Service ID from the live tenant
4. Enable rows, set thresholds, save

1. Set Metric = * and/or Service name = * to match all
2. Use only service labels returned by data collection. Do not invent service names.

Narrows which datapoints a row matches. All clauses must match (AND). Matching is case insensitive. Malformed clauses are silently ignored.

Example filter value:

request:/SDF/AJM_EXECUTE_EXM,requestType:RFC

1. No rows configured: publish all metrics. No filtering. Backward compatible.
2. Service name: glob matched against RUM service label. S4H* matches S4H.100. * matches all.
3. Metric: exact match only. * matches all types. Partial globs like *Status do NOT work.
4. Attributes Filter: all clauses must match. Empty = match all datapoints.
5. Exclusive = true: datapoint consumed by first matching row. Later rows skip it.
6. Metric = false: row evaluates alarms but publishes no metric datapoints.

Base key: promonitor.cloud_alm.rum.*

Tags published with each datapoint: service.name sap.service.name service.namespace service.instance.id sap.service.display_name request requestType user microService

No rows needed. Empty table = publish everything.

Other metric types for S4H.100 are not published.

All six metric types published. Only datapoints where request = /SDF/AJM_EXECUTE_EXM.

Metric = false: alarms fire but no datapoints written to time-series.

Row 1 consumes datapoints for first request (Exclusive = true). Row 2 handles second request independently.

Only requests metric published. Only datapoints where requestType = RFC.

• Metric field does not support partial glob patterns. *Status does NOT match criticalStatus. Use exact values or *.
• Service ID is auto-populated. Manual entry not supported.
• Malformed Attributes Filter clauses are silently ignored. Validate format before saving.
• Exclusive = true means first matching row wins. Order rows from most specific to most general.
• Thresholds apply to the raw numeric value of the selected metric.