Integration Telemetry
Route: /org/resolve/integration · Permission: Allows viewing Integration Telemetry charts and settings
1. What it is
The health of everything arriving over the API — success rate, latency and the raw hit log.
2. What is on screen
| Panel | Shows |
|---|---|
| All API Keys | Every credential and its state |
| Ingress Success Rate | Proportion of inbound calls accepted |
| Avg Execution Latency | How long Orbit took to process them |
| API Synchronization Traffic Trend | Volume over time |
| API Hit Ingress History Logs | Per call: Hit Time · Client IP · Ingress Request · Latency · Detailed Status Message |
Filterable by status; searchable by IP or path.
Three failure shapes, distinguished here
Nothing logged — the call never arrived; debug the sender. Logged and rejected — read the status message. Logged, accepted, wrong result — the integration works but sends the wrong payload. Only this screen tells them apart.
3. Don't confuse this with…
| These two | Differ by |
|---|---|
| Integration Telemetry vs API Integration | Charted health vs issuing and revoking keys |
| Ingress vs fulfilment webhooks | Inbound to Orbit vs outbound from it |
| Integration Telemetry vs AI Governance | API traffic vs AI spend |
4. Troubleshooting
| Symptom | Cause |
|---|---|
| Success rate dropped | Read the status messages in the hit log |
| Latency climbing | Large payloads or a downstream slowdown |
| Traffic fell to zero | The sender stopped, or its key expired |