SAP (APM-001)
Watchtower connects to SAP NetWeaver and S/4HANA instances through the agent's sap module, which calls the documented SAPControl web service of sapstartsrv. No SAP-side add-on is installed.
modules:
sap:
url: http://127.0.0.1:50013 # https://host:5<NN>14 for TLS
username: sapadm # OS user with SAPControl read rights
password: ${env:SAP_PASSWORD} # agent secret reference, never project config
service: erp-prd # stamped as `service` on every SAP series (default "sap")
long_running_s: 300 # a work process running this long counts as stalledWithout username and password the module stays inert: it validates nothing and never dials the instance, so shipping the manifest's defaults is safe.
Series: sap.process.status/count (GetProcessList), sap.workprocess.count/utilization and sap.workprocess.long_running (ABAPGetWPTable), sap.queue.length/high/max per dispatcher queue (GetQueueStatistic), and wt.integration.up{integration="sap"}. Because they carry service, they sit next to that service's traces and RED metrics.
Starter alerts in integrations/sap/manifest.yaml: process not green, dialog work processes exhausted, dialog steps stalled, instance unreachable.
Not covered: ABAP-internal business transaction traces (the AppDynamics ABAP agent's code-level view) need an add-on inside the SAP kernel; we do not ship one.