SAP connections

A SAP connection defines the SAP system, assigned connector, and collections that runtime extracts. Data Streams and credentials are resolved by the server.

The saved password is bound to the assigned connector plus ASHOST, SYSNR, client, and RFC user. You can edit the alias, language, time zone, or collections without re-entering it. Changing any of those five trust fields requires a new password; ******** or an empty field cannot reuse the previous credential for another runtime or SAP system.

Seven collections

Collection	Default	Result
Metrics	300 s	CCMS and Operations metrics
CCMS events	300 s	Normalized events
Jobs	300 s	Job runs and job logs
Work processes	300 s	Process snapshots
ABAP dumps	300 s	Sanitized ST22 dumps
RFC failures	300 s	RFC failures/recoveries without payload
Certificates	86400 s	Certificate inventory and transitions

Each control can be enabled and scheduled independently. The interval is a wall-clock-aligned fixed frequency, not a delay that starts when the previous extraction ends. At 300 seconds, all seven families start at deterministic phases within the first minute of each five-minute block. Every source/family has its own worker, so a slow CCMS or Jobs read cannot delay Metrics, Work Processes, or the heartbeat. Startup and configuration reload perform one staggered bootstrap extraction without waiting a full interval; missed cycles coalesce instead of building a backlog.

Capabilities

The card separates Scoped telemetry from connector heartbeat: data is available only when a v2 document exists for that exact source. Each collection distinguishes No source data yet—a successful lookup with no documents—from Source data status unavailable—a lookup that could not be completed—without exposing Elasticsearch implementation details. Each collection shows its current state, Last success, and Last check. An earlier error disappears after a successful collection; Details folds the latest sub-capability result rather than presenting an error history. One unsupported collection does not block the others.

Dumps never include memory/business data, RFC never includes call payloads, and certificates expose public metadata only—never private keys.

Assign a connector with a recent heartbeat, save the source, wait for the applied configuration revision, and verify Metrics/Events plus Job Monitoring, Certificates, and RFC & Integrations. Agent upgrade required means the producer must be upgraded to 2.0; it is not a valid zero.