Observability

Warning

Beta Notice: COS for robotics is currently in beta. Content and features may change, and some functionality may be incomplete or experimental. Feedback is welcome as we continue to improve.

COS for robotics stands for Canonical Observability Stack for robotics, and is a superset of COS Lite.

This section explains how Canonical’s observability framework extends to robotic systems—connecting devices, applications, and cloud components into one monitoring and data-sharing pipeline.

• What is COS for robotics
  • How COS for robotics works
    • The server side
    • The device side
  • Who is COS for robotics for
• Alert rules configuration from device
  • Rules uploaded on the COS-registration-server
    • Templated alert rule files format
  • Alert rule files’ flow from device to COS-registration-server and the applications
• COS for robotics components
  • Server components
    • cos-registation-server-k8s
    • foxglove-studio-k8s
    • ros2bag-fileserver-k8s
  • COS Lite components
  • Devices components
    • cos-registration-agent
    • foxglove-bridge
    • ros2-exporter-agent
    • rob-cos-data-sharing
    • rob-cos-grafana-agent
    • rob-cos-demo-configuration
• Security considerations for COS for robotics
  • Handle CA distribution carefully
  • Protect access to the Juju TLS model
  • Understand the scope of system-wide CA trust on devices
  • Device leaf certificates are not automatically renewed
  • There is no certificate revocation mechanism for devices
  • Device private key is protected by snap isolation, not encryption at rest
  • Foxglove bridge WebSocket is accessible on the local network
  • Ubuntu Core devices cannot use system-wide CA distribution