oma-observability

Solid

Intent-based observability + traceability router across layers, boundaries, and signals. Routes to vendor-specific skills via category taxonomy; owns transport tuning, meta-observability, incident forensics. Use for observability, traceability, telemetry, APM, RUM, metrics, logs, traces, profiles, SLO, incident forensics, tracing architecture work.

AI & Automation 1,081 stars 126 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%

100

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Observability Agent - Intent-based Router ## Scheduling ### Goal Route, design, tune, and review observability work across MELT+P signals, layers, boundaries, vendor categories, transport choices, meta-observability, and incident forensics. ### Intent signature - User asks for observability, telemetry, OTel, metrics, logs, traces, profiles, SLOs, RUM, APM, incident forensics, trace propagation, transport tuning, or observability-as-code. - User needs vendor/category routing or observability architecture instead of a single vendor's already-covered setup. ### When to use - Setting up an observability pipeline (OTel SDK + Collector + vendor backend) - Designing traceability across service and domain boundaries (W3C propagators, baggage, multi-tenant, multi-cloud) - Tuning transport layer (UDP/MTU, OTLP gRPC vs HTTP, Collector DaemonSet vs sidecar topology) - Running incident forensics (6-dimension localization: code / service / layer / host / region / infra) - Selecting a vendor category (OSS full-stack vs commercial SaaS vs high-cardinality specialist vs profiling specialist) - Implementing observability-as-code (Grafana Jsonnet dashboards, PrometheusRule CRD, OpenSLO YAML, SLO burn-rate alerts) - Meta-observability (pipeline self-health, clock skew detection, cardinality guardrails, retention matrix) - Covering the MELT+P signal set: metrics, logs, traces, profiles (OTEP 0239), cost (OpenCost), audit (SOC2/ISO), privacy (GDPR/PIPA) - Migrating off deprecated tools (Flue...

Details

Author: first-fluke
Repository: first-fluke/oh-my-agent
Created: 4 months ago
Last Updated: today
Language: TypeScript
License: MIT

Integrates with

Grafana · Monitoring gRPC · API

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

observability-architect

Application-side observability — structured logs, Prometheus metrics, OTel traces, signal correlation, head sampling, PII discipline, RED+USE. Use when instrumenting code, naming metrics, or auditing what a service emits.

2 Updated yesterday

ralvarezdev

AI & Automation Listed

observability

Use for observability, logs, metrics, traces, health checks, dashboards, alerts, and SLOs.

1 Updated 6 days ago

kreek

AI & Automation Listed

pattern-engineer-observability

OpenTelemetry is the only instrumentation API in source; vendor SDKs only behind the Collector. Services emit traces + metrics + logs through OTel with shared resource attributes, W3C `tracecontext` propagation, auto-instrumentation for boilerplate, RED/USE metrics with bounded label cardinality, structured JSON logs gated at source. Activate when touching instrumentation or `OTEL_*` env vars.

0 Updated yesterday

MartinKChen