Orchestration Analytics
Measure success rate, latency, and cost by route and by provider to continuously optimize your rules.
6 min read
Orchestration is only valuable if you measure it. The Dashboard exposes, per route and per provider, the indicators that guide your rules.
Key indicators
success_ratepercentageoptionalShare of successful attempts, by provider and by route.
avg_latency_msintegeroptionalAverage acceptance latency per provider.
fallback_ratepercentageoptionalShare of transactions that required a fallback.
cost_per_txnamountoptionalAverage cost per successful transaction, by route.
Comparing providers
Konsole·Log Explorer
status:5xx OR provider:"MTN MoMo"
24hMéthodeEndpointStatutDuréeProvider
ROUTE
momo-cm-mtn-first → MTN MoMo200412ms98.4%ROUTE
momo-cm-mtn-first → Orange Money200690ms95.1%ROUTE
large-amounts → Bank2001840ms99.2%ROUTE
small-amounts → Wave402980ms91.7%Closing the optimization loop
- Spot a provider whose
success_rateis dropping or latency is rising. - Reorder your rules to downgrade it.
- Test in sandbox, then publish.
- Monitor the
fallback_rate: a high rate reveals a fragile primary provider.
Export for your own analysis
Metrics are exportable as CSV from the Dashboard and accessible via API to feed your own dashboards (see Dashboard → Reports).