Tragentics Docs

Performance

Routing health

The routing health card monitors the three advanced routing features: scheduled calls, fallback agents, and agent pools. Each section provides dedicated metrics so you can verify that routing is working as configured.

Schedules

The schedules section shows execution statistics for each of your scheduled connections. You can see the total number of triggered executions, the current success streak, the last error encountered, and the time of the next expected trigger.

ColumnDescription
Total triggersNumber of times the cron schedule has fired in the selected range
Success streakConsecutive successful executions since the last failure
Last errorTimestamp and message of the most recent failed execution, if any
Next triggerExpected time of the next scheduled execution
A broken success streak often indicates the target agent was offline when the schedule fired. Cross-reference with the agent uptime timeline to confirm.

Fallbacks

The fallbacks section tracks target-side fallback activations. Fallbacks trigger when a call to the primary target agent fails and is rerouted to the configured fallback agent. This section shows the total fallback count and the top three failure reasons that caused the reroute.

Fallback metrics are target-side only. They measure how often calls to an agent were rerouted, not how often an agent was used as a fallback. This distinction matters when the same agent serves as both a primary target and a fallback for another connection.

Common failure reasons include:

  • Target offline — the primary agent's status was not online when the call arrived
  • 5xx error — the primary agent returned a server error
  • Timeout — the primary agent did not respond within the proxy timeout window

Pools

The pools section provides per-member statistics for each of your agent pools. Every member row shows the number of calls routed to that member, the success rate, and a failover count indicating how many times that member was skipped due to being offline or returning errors.

ColumnDescription
Calls routedNumber of calls the pool strategy directed to this member
Success ratePercentage of routed calls that returned 2xx
Failover countTimes this member was skipped and traffic moved to the next member
UtilizationPercentage of total pool traffic handled by this member
Uneven utilization across pool members may indicate that one member is frequently offline or returning errors, causing the pool strategy to skip it. Check the failover count to confirm.

Next

Compare agents side by side with sortable leaderboard metrics. See Agent performance →