Skip to main content

13 RFC & Integrations

This view investigates failed integrations without collecting call payloads.

Anonymized RFC failure control center
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.
  • 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.

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​

tRFC/aRFC, inbound/outbound qRFC, and bgRFC are probed independently. An unauthorized or unavailable sub-capability does not block the others. An older producer reports Agent upgrade required.