13 RFC & Integrations

This view investigates failed integrations without collecting call payloads.

The view preserves protocol, direction, destination, age, and lifecycle without collecting payloads.

What it shows

• Active and recovered failures by protocol and direction.
• Destination, queue, function, state, age, and technical error.
• Filters by protocol, lifecycle, host, time range, and text.
• The selector offers only protocols present in the range summary: classic traffic is shown as tRFC/aRFC, while qRFC or bgRFC appear only when they have observations.
• The ledger is globally ordered by age from newest to oldest, including across page boundaries.
• Paginated history for each failure and recovery.
• Links from Events to the exact evidence.
• Current Total/Active/Recovered/Protocols summary and the standard SPOT search control.
• RFC failure details with state, function, code, technical message, and lifecycle; call payloads are never shown.

The Total, Active, Recovered, and Protocols KPIs describe the SAP source and global time range. Protocol, lifecycle, and search filter only the ledger. Changing any of those filters returns to the first page and closes the previous detail so it cannot be confused with the new result. An initial failureId deep link remains valid until a filter changes.

rfc-failures counts unique IDs per bucket, protocol, and direction. Warning starts at 1 and critical at 5 within 15 minutes; sparse ML can add context for intermittent patterns.

Partial capability

The producer reports classic RFC, inbound/outbound qRFC, and bgRFC availability independently. An unauthorized or unavailable sub-capability does not block the others. The filter displays only protocols with positive data for the current source and range. An older producer reports Agent upgrade required.