Retrieves job execution metrics from SAP Cloud ALM Job & Automation Monitoring (JAM). Publishes time-series metrics and evaluates alarms per configured row.

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

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.jam.read
• $XSMASTERAPPNAME.calm-api.metrics.read

• Publishes eight metric types per JAM datapoint: run_time average_run_time executions success warning aborted application_warning application_error
• Time window is derived from the monitor schedule: from = now - schedule_interval, to = now (format yyyyMMddHHmmss UTC)
• Paginated fetching up to 3000 records per page using x-total-count response header
• 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)
• Optional alarm tag for grouping or routing
• Auto-clear when alarm condition no longer matches
• Load Services button: auto-discovers JAM service IDs and names from the live tenant

Data collection populates Service name and Service ID from the Cloud ALM JAM service registry.

Always run data collection before adding rows. A service name not returned by data collection may not match what the metrics API returns.

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 names returned by data collection

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

Example filter value:

jobtype:ABAP,servicetypelabel:SAP S/4HANA

1. No rows configured: nothing is published. Add at least one active row to collect data.
2. Service name: glob matched against JAM service label. MY_SERVICE* matches MY_SERVICE.100. * matches all.
3. Metric: exact match or *. Partial globs 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.jam.*

Tags published with each datapoint: service_name sap_service_name service_namespace service_instance_id sap_service_display_name plus datapoint-level tags jobname jobtype jobtypelabel servicetype servicetypelabel

Alarms use a suppression key to deduplicate. Format:

• With job name: {monitorId}_{connectorId}_alm_jam_{service}_{metric}_{jobName}_{rowIdx}
• Without job name: {monitorId}_{connectorId}_alm_jam_{service}_{metric}_{rowIdx}

One alarm per unique key. A new execution value overwrites the previous alarm state for the same key.

Set Service name = * and Metric = *. An empty table sends nothing.

Value is in ms. G2W:300000 = warning above 5 min. W2M:600000 = major above 10 min.

Alarms as soon as 1 aborted job appears. G2W:1 means any non-zero value triggers warning.

Only ABAP job datapoints evaluated. Other job types not matched.

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

Row 1 consumes MY_SERVICE datapoints (Exclusive = true). Row 2 applies a looser threshold to all other services.

Each metric type gets its own threshold and alarm tag.

• Metric field does not support partial glob patterns. *Error does NOT match application_error. Use exact values or *.
• Service ID is auto-populated by data collection. Manual entry is possible if the UUID is known.
• Malformed Attributes Filter clauses are silently ignored. Validate format before saving.
• Time window resolution depends on the monitor schedule. If the schedule interval is larger than the JAM data retention window, some executions may be missed.
• Exclusive = true means first matching row wins. Order rows from most specific to most general.