What problem does it solve?
Observability prevents blind operations by making robot and infrastructure issues measurable and actionable through monitoring, alerting, and traceable signals.
Core Features & Use Cases
- Prometheus metrics and alerting: Collect time-series metrics (e.g., node, ROS2 endpoints, NATS) and trigger alerts like offline robots, low battery, and high topic latency.
- OpenTelemetry traces and metrics: Instrument ROS2 services to emit vendor-neutral tracing and telemetry to an OTel Collector for centralized analysis.
- Netdata real-time monitoring and dashboards: Provide fast, interactive system views and custom ROS2 plugin-style data surfaces, with Grafana dashboards for battery, message rate, and latency percentiles.
Use case: You deploy a fleet of ROS2 robots and need early warning when robots go offline, batteries drop below a threshold, or command/topic latency starts trending upward—while also capturing traces for diagnosing which service or operation caused the slowdown.
Quick Start
Use the observability skill to set up Prometheus scraping plus alert rules and an OpenTelemetry pipeline so you can visualize robot health and latency in Grafana immediately.