Skip to Content

Monitoring and Visibility

Monitoring is the operational entry point for RocketAiFlow. Start here to check outbound campaign execution, telephony readiness, platform health, and the evidence behind a live issue.

Use dashboards first for real-time state and selected time-range trends. Use Dialer Dashboard Panels when you need to interpret a specific metric, then move to logs and traces when you need event-level evidence.

Operating model

Open Monitoring when a campaign, trunk, endpoint, host, container, database, or API action needs operational verification. Start from the symptom and follow the evidence to the layer that owns the issue.

Start with the Dialer dashboard for campaign state and outcome quality. Use platform dashboards when the symptom points to telephony, containers, database, or host pressure. Move to logs and traces when you need the exact event path, timing, or downstream behavior.

  • Open Pre-Provisioned Dashboards for live campaign state, Dialer performance, telephony readiness, Asterisk, containers, MySQL, and host visibility.
  • Open Dialer Dashboard Panels when a specific Dialer metric needs interpretation.
  • Open Logs and Traces when you need event detail, service timing, API action behavior, or OpenTelemetry correlation.
  • Open Call Records from the workflow area when you need the result of a specific call, transcript, recording state, or timing.

What to use

Outbound campaign monitoringUse the Dialer dashboard. It is the main outbound control room for campaign status, active calls, call limits, dialing rate, outcomes, and selected time-range performance.
Trunk and endpoint readinessUse Real-Time Agents & Trunks inside the Dialer dashboard. It shows whether endpoints and trunks are available, not in use, in use, unavailable, or invalid.
Panel-level interpretationUse Dialer Dashboard Panels to interpret Total Outcomes, Call Outcomes, dialing rate, call volume, endpoint state, talk time, ring time, and selected-range performance.
Telephony and platform healthUse Asterisk Overview, Asterisk Log, cAdvisor, MySQL, and Node Exporter dashboards. These views help separate workflow issues from telephony, runtime, database, container, or host pressure.
Deeper investigationUse Logs and Traces when a dashboard shows a symptom but you need to understand the event, service path, timing, or downstream API behavior behind it.

Dialer real-time signals

During a live outbound run, the first question is whether the campaign is actually producing calls and outcomes. The Dialer dashboard answers that with campaign status, active calls, call limits, dialing rate, outcome totals, and selected-range performance.

Real-Time Agents & Trunks is part of the same operational view because it separates campaign behavior from telephony readiness. If campaigns look healthy but calls are not moving, endpoint and trunk state are the next place to check.

  • If Dialer Status shows calls in progress, the campaign is actively generating calls.
  • If Real-Time Agents & Trunks shows the selected trunk as Not In Use, it is available; when calls are active it should move to In Use.
  • If endpoints are Unavailable or Invalid, investigate trunk, registration, provider, or endpoint configuration before changing campaign pacing.
Pre-Provisioned DashboardsReview the Dialer, Asterisk, cAdvisor, MySQL, and Node Exporter dashboards.Dialer Dashboard PanelsRead the Dialer panel guide when operators need metric-by-metric guidance.Logs and TracesUse OpenTelemetry-based logs and traces when a dashboard symptom needs evidence.TroubleshootingUse setup checks when monitoring points to a workflow configuration issue.
Last updated on
Quickstart