observability-operator

Instrument services with structured telemetry and validated alerting.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill observability-operator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-operator
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/observability-operator
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill observability-operator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the hands-on work of making services observable, dependable, and measurable by wiring real telemetry, truthful health checks, and actionable alerting.

Core Features & Use Cases

  • Structured instrumentation: Add logs, metrics, traces, correlation IDs, tenant context, and redaction before emission.
  • Operational validation: Verify that telemetry actually arrives and behaves correctly by running real queries and checking observed data.
  • Alert and dashboard operations: Create or edit dashboards, alert rules, and health checks with required metadata such as severity, owner, runbook link, and threshold justification.
  • Noise reduction: Tune noisy alerts, add deduplication, and apply bounded silences with owner and expiry.
  • Use case: A service was deployed and the alerting is noisy, so this Skill updates instrumentation, confirms visibility in the backend, and cleans up the alert paths without redesigning SLO policy.

Quick Start

Ask the observability operator to instrument the service, verify telemetry with real queries, and update the related dashboards and alerts according to the existing reliability design.

Frequently Asked Questions about observability-operator

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

FAQPage Schema
How do I reduce noisy alerts and add deduplication for my deployed services?

Telemetry verification confirms logs, metrics, and traces actually arrive by running real queries against operational backends. This validates observed data behavior instead of assuming instrumentation works correctly after deployment.

How do I add structured telemetry and correlation IDs to my service instrumentation?

Add structured telemetry by instrumenting services with logs, metrics, traces, correlation IDs, tenant context, and redaction before emission. This ensures observability data is consistent and secure across backends.

What metadata is required for creating actionable alert rules and health checks?

Actionable alert rules and health checks require metadata including severity, owner, runbook link, and threshold justification. This completeness ensures alerts are trustworthy and maintainable during operations.

Can I use this approach to update dashboards and alerts without changing my SLO policy?

Yes, you can update dashboards, alert rules, and health checks without redesigning SLO policy. This approach focuses on post-deploy observability work, noise reduction, and telemetry verification rather than policy design.

Why should I bound metric labels and apply redaction before emitting telemetry?

Bounding metric labels prevents cardinality explosions, while redaction before emission protects sensitive data. These constraints ensure telemetry remains performant, secure, and trustworthy across operational backends.