ServiceServicetypeA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

SAP Monitoring Service for SAP BTP

Metrics, availability and JMX checks, and email or webhook alerts for Java, HTML5 and SAP HANA XS applications and database systems, in Neo regions of SAP BTP.

SAP Monitoring Service for SAP BTP reads the status and metrics of a running Java app and its processes, an SAP HANA XS app or an HTML5 app, and the metrics of a database system, with their history in the SAP BTP cockpit. It registers availability checks for Java and SAP HANA XS applications, JMX checks and operations on JMX MBeans for Java applications, and custom HTTP checks for HTML5 and SAP HANA XS applications. Alerts go to an email channel, for one application or for every application and database system in a subaccount, or to a webhook, and everything is reached through the cockpit, the console client, or the Metrics, Checks and Alerting Channels REST APIs. Twelve of the fourteen regions SAP lists for the service are Neo regions, and the service in Neo is being removed from the Eligible Cloud Services List on 31 December 2028, by SAP's notice on its Default plan.

Where it sits

Lives in
Provides
TelemetryBTPTelemetrycapabilitySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.Operations automationBTPOperations automationcapabilityActing on a running landscape without someone at the console: an alert routed to where a person or a system will pick it up, and a command that troubleshoots or remediates when it arrives. [Logging](capability:logging), [telemetry](capability:telemetry) and [health checks](capability:health-checks) observe; this acts on what they report. Running an application's own recurring work is [job scheduling](capability:job-scheduling).

Who is behind it

SAPSAPOrganisationMaintains this
In the atlas: maintains 137, wrote 14
@SAP
maintainer

What it declares

Every artifact

Type
Service
Origin
By SAP

Connections2

What’s New6

from SAP Help Portal, read
help.sap.com/whats-new, Monitoring ServiceOn SAP Help Portal
6entries since , per month
  1. REST APIs

    ChangedGeneral AvailabilityInfo onlyNeorevised 2025-07-21

  2. New MBean Attribute for Certificates

    NewGeneral AvailabilityInfo onlyNeorevised 2024-05-10

  3. Use of Comments for Documentation Feedback

    NewGeneral AvailabilityInfo onlyNeo

  4. New Certificate Validity Metric

    NewGeneral AvailabilityInfo onlyNeo

  5. Managing Thresholds in SAP BTP Cockpit

    NewGeneral AvailabilityInfo onlyNeorevised 2023-07-05

  6. Checks REST API

    ChangedGeneral AvailabilityInfo onlyNeorevised 2024-01-01

titles and labels, read

Others providing8

Telemetry
  1. SAP Cloud LoggingOpenSearch-based store for logs, metrics and traces
  2. Agent Activation for Dynatrace Service for SAP BTPInjects the Dynatrace agent into Java applications on SAP BTP
  3. @sap/e2e-traceSAP Passport handling for Node.js components
  4. @saptools/cf-metricsRead-only query tool for metrics in SAP Cloud Logging
  5. @saptools/cf-otelRead-only query tool for OpenTelemetry spans in SAP Cloud Logging
Operations automation
  1. SAP Alert Notification service for SAP BTPPublishing and subscribing to alerts about BTP resources and apps
  2. Application AutoscalerScales Cloud Foundry app instances by policy rules and schedules
  3. SAP Automation PilotRuns operations commands on BTP by hand, schedule or event

Details

Sources1
Added by handdiscovered herechecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, operations-and-runtime
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:btp-monitoring
JSON
/artifacts/btp-monitoring.json
MCP
Connecting an agent