agent-observability

Name: agent-observability
Availability: InStock
Author: fabiomilennials1234-a11y

Collect logs, metrics, and traces to detect performance degradation and errors.

Updated Jan 29, 2026

Search Tags:#logging #metrics #observability #alerts #postmortem #sre #sli

Ready to run

npx skills add https://github.com/fabiomilennials1234-a11y/v8milennialsb2bv2 --skill agent-observability-fabiomilennials1234-a11y

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-observability
Source: https://github.com/fabiomilennials1234-a11y/v8milennialsb2bv2/tree/main/.claude/skills/agent-observability
Command: npx skills add https://github.com/fabiomilennials1234-a11y/v8milennialsb2bv2 --skill agent-observability-fabiomilennials1234-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observability ensures you know when something is wrong in production by instrumenting logs, metrics, traces, and alerts so you can respond before customers are impacted. Logs without aggregation are entropy; alerts without thresholds are noise; dashboards without SLIs are decorative.

Core Features & Use Cases

Instrumentation: Sentry config, runtime_logs schema, structured logging with correlation_id
Metrics & Use Cases: latency, error rate, and SLO definitions
Dashboards & Runbooks: operational dashboards and documented incident response
Incident response: blameless post-mortems and runbooks
Validation & governance: correlation_id, guarded logging, and alert routing

Quick Start

Set up a basic instrumentation plan (logs, metrics, and traces), define a simple SLI/SLO, and configure alerts and a runbook to start monitoring production health.

Frequently Asked Questions about agent-observability

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

FAQPage Schema

How do I set up observability for API endpoints and cron jobs?▼

Observability instrumentation requires Sentry or Supabase integration alongside structured logging with a correlation_id. You collect logs, metrics, and traces across edge layers, APIs, cron jobs, and data pipelines to detect errors and latency hotspots.

What's the best way to define SLI and SLO thresholds for production alerts?▼

Defining SLI and SLO thresholds requires measuring latency and error rates to configure actionable alerts. This approach prevents noise by ensuring alerts only fire when performance degradation threatens established service level objectives.

Can I use Sentry and Supabase for structured logging and alert routing?▼

Yes, Sentry and Supabase integration supports structured logging and alert routing. You use a runtime_logs schema with a correlation_id to aggregate logs and route alerts to appropriate responders before customers are impacted.

Why do I need a correlation_id in my logging and metrics setup?▼

A correlation_id in logging and metrics traces requests across edge, API, and pipeline components. This guarded logging practice validates data governance and links logs to metrics, reducing entropy and making incident root causes identifiable.

How do you run a blameless post-mortem after an incident response?▼

Running a blameless post-mortem after incident response involves documenting the event using operational dashboards and runbooks. This governance practice analyzes collected traces and metrics to prevent future recurrence without attributing individual fault.