Skip to main content

​
Monitoring

AgentVerse logs every orchestration execution in full detail — inputs, outputs, errors, and timing at both the run level and the individual node level. Use the monitoring panel to debug issues, verify behaviour, and track performance over time.

​
Orchestration Runs

Open any orchestration and click the Runs tab to see all past and in-progress executions.

​
Run Statuses

​
Filtering Runs

Narrow the list using:

​
Run Detail View

Click any run row to open the Run Detail panel. This shows everything that happened during that execution.

​
Run Summary

​
Node Execution Trace

The trace shows every node that ran, in order: Click any node row to expand and inspect its full input and output payloads as JSON. This is the primary tool for debugging unexpected node behaviour.
When debugging, expand both the input and output of the failing node side by side. The input tells you what data the node received; the output (or error) tells you what went wrong.

​
Re-running Failed Runs

To retry a failed orchestration:
  1. Find the failed run in the Runs panel.
  2. Click the Re-run button (replay icon) on the right.
  3. The orchestration restarts from the beginning using the same original trigger data.
Re-runs create a new Run ID and are logged as a separate entry — the original failed run is preserved. This means you can compare the re-run trace against the original to confirm the fix.

​
Alerts and Notifications

Configure alerts to be notified automatically when an orchestration fails or exceeds a duration threshold.

​
Setting Up Alerts

  1. Open the orchestration and navigate to Settings → Alerts.
  2. Click Add Alert.
  3. Configure the alert rule:

​
Alert Payload

Every alert includes:
  • Orchestration name and ID
  • Run ID
  • Failed node name and error message
  • Direct link to the run detail page
Set a cooldown period for high-frequency orchestrations to avoid alert fatigue. A cooldown of 5–15 minutes is typical for production orchestrations.