Monitoring and Troubleshooting
Expanso Cloud brings fleet, pipeline, component, and execution information into the same workspace. Start with the scope of the problem, then narrow the view to the affected version, node, or component.
Choose the right view
| View | What you can inspect |
|---|---|
| Nodes | Connected, disconnected, and lost nodes, host details, and agent versions. |
| Node Monitoring | CPU utilization and memory usage over a selected time range. |
| Pipeline Monitoring | Input bytes, output bytes, and orchestration errors, with deployment context. |
| Selected pipeline component | Component-appropriate byte metrics and processor latency percentiles. |
| Deployment detail | Release progress, version-specific executions, and event timeline. |
| Pipeline Logs | Live logs from a selected connected node. |
Use the time-range and refresh controls to investigate a period of interest. Metrics arrive on an export interval, so a recent operational change may appear in the charts after a delay.
Processor latency describes processing at that component. Do not interpret it as source-data freshness or end-to-end delivery latency unless your pipeline measures those quantities explicitly.
Follow a failure from rollout to execution
- Open the pipeline and check its status and deployment context.
- If the issue began with a release, inspect that deployment's progress and compare the configuration with the previous version.
- Open the affected execution and identify its node and reported state.
- Check the node's connection state, recent heartbeat, CPU, and memory.
- Inspect component traffic and, for processors, latency to narrow the affected processing step.
- Tail logs from the connected node to investigate the current error.
This workflow connects a release to its running instances. A healthy control-plane response or accepted job submission alone does not prove successful output. Verify delivery at the destination when that is the outcome you need.
Stream live logs
Open the pipeline's Logs view, select a node, and start streaming. Use severity and text filters to focus the display. You can stop streaming, clear the displayed entries, and control auto-scroll.
Live streaming requires a connected node and supported versions of both the workspace runtime and Expanso Edge. The current minimum for this feature is v2.1.18 on both sides. Unknown or unsupported versions disable the stream; contact support if you need help checking your workspace's version.
The browser keeps up to 10,000 streamed entries. This is a live troubleshooting view, not a promise of historical log retention or a durable archive. Logs may contain payload values or sensitive diagnostics, so configure pipeline logging with that in mind.
Integrate with your observability tools
Use the OpenTelemetry guide for documented telemetry export patterns. The Cloud console's built-in charts and an external observability platform have different controls; configure alert rules and retention in the system responsible for them.
For pipeline recovery behavior, use the specific troubleshooting guides and the relevant component references. Cloud visibility helps diagnose a failure; delivery and checkpoint behavior still depend on the pipeline's inputs, processing, buffering, and outputs.
