#observability
3 skills & prompts · 1 tools · 10 MCP servers · 1 articles
Skills & prompts
observability
Use when instrumenting a system or when an incident cannot be diagnosed from existing telemetry. Covers structured logging, metrics, distributed tracing, SLOs, and alerts that are worth waking someone for. Trigger on "we couldn't tell what happened from the logs", "add tracing to
dcc-diagnostics
Infrastructure skill — DCC-agnostic observability primitives: generate error reports, capture screenshots, query audit logs, inspect tool performance metrics, and monitor process health. Works in any DCC environment (Maya, Blender, Houdini, Unreal, etc.) or standalone Python. Cal
dcc-diagnostics
Infrastructure skill — DCC-agnostic observability primitives: capture screenshots, query audit logs, inspect tool performance metrics, and monitor process health. Works in any DCC environment (Maya, Blender, Houdini, Unreal, etc.) or standalone Python. Use for debugging any skill
Tools
MCP servers
Ask an agent why a PHP site is slow: every request with its SQL, HTTP calls, errors and N+1.
Read the logs, metrics, and traces of the app you are editing, from the Loggerhead Mac app.
Query your AI agents' traces, errors, cost and alerts in Rius, the agent observability platform.
Read issues, logs, traces, metrics, releases, and analytics from approved LogBrew projects.
Read your Condux issues, events and stack traces (deminified with source maps). Triage optional.
Articles
The control plane was flapping because of a spinning disk
Healthy nodes, a quiet network, 300 restarts in three days, and a latency budget measured in milliseconds