observability

Collect metrics, traces, and system views for robotics observability.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/drdave-flexnetos/ripple-env --skill observability-drdave-flexnetos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/drdave-flexnetos/ripple-env/tree/main/.claude/skills/observability
Command: npx skills add https://github.com/drdave-flexnetos/ripple-env --skill observability-drdave-flexnetos

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up ROS2 monitoring for robot fleet health and latency?

Setting up ROS2 monitoring requires Prometheus scrape configuration for time-series metrics, OpenTelemetry SDK instrumentation for service traces, and Grafana or Netdata dashboards to visualize robot health, battery levels, and topic latency.

Can I trigger alerts when a ROS2 robot goes offline or battery drops?

Yes, triggering alerts for offline robots or low battery is achieved by defining alert rules in Prometheus using scraped metrics from ROS2 endpoints and nodes, enabling early warning for fleet failures.

Does OpenTelemetry work with ROS2 services for distributed tracing?

OpenTelemetry works with ROS2 services by instrumenting them to emit vendor-neutral traces and telemetry to an OTel Collector, enabling centralized analysis of which service operations cause latency slowdowns.

What is the best way to visualize ROS2 message rate and latency percentiles?

Visualizing ROS2 message rate and latency percentiles is best done using Grafana dashboards populated with Prometheus metrics and Netdata real-time system views, providing interactive custom data surfaces.

Do I need Netdata and Grafana together for robotics observability?

Netdata and Grafana are not strictly required together; Netdata offers fast interactive real-time system views while Grafana handles broader dashboarding, and Netdata is optional for end-to-end observability.