observability-engineer

Designs logs, metrics, alerts, and tracing strategies aligned to the existing system stack.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/SleyiW/iWana-neXt --skill observability-engineer-sleyiw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-engineer
Source: https://github.com/SleyiW/iWana-neXt/tree/main/.agents/skills/observability-engineer
Command: npx skills add https://github.com/SleyiW/iWana-neXt --skill observability-engineer-sleyiw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Systems often lack useful operational visibility: logs leak sensitive data, metrics are vanity numbers, and alerts create noise instead of action. This Skill helps you design gradual, realistic observability for the iWana neXt stack without assuming enterprise-grade infrastructure that does not exist. ## Core Features & Use Cases - Observability Strategy Design: Define structured logs, actionable metrics, healthchecks, and basic SLIs for critical components. - Traceability Review: Audit error, job, retry, and sensitive-write flows to ensure they leave sufficient operational evidence without mixing tenants. - PII-Safe Logging Rules: Enforce zero-trust PII handling so logs and metrics never contain secrets, tokens, or full sensitive payloads. - Use Case: Before launching a new async job pipeline, use this Skill to define correlation IDs, backlog metrics, and a minimal set of actionable alerts with clear owners. ## Quick Start Review the current logging and monitoring setup of this service and propose a gradual observability plan with actionable alerts and PII-safe logs.

Frequently Asked Questions about observability-engineer

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

FAQPage Schema
How do I design an observability strategy for an existing backend system?

Start from the real stack rather than a hypothetical platform. Define structured logs with correlation IDs, metrics tied to critical flows like latency and error rate, and a few actionable alerts with clear owners before adding new tooling.

How to make application logs safe from PII and secret leakage?

Apply zero-trust PII rules to logs and metrics: never record real personal data, secrets, tokens, or full sensitive payloads. Sanitize events and errors before persisting or exporting them.

What metrics should I track for critical backend flows?

Measure health, latency, error rate, and backlog where applicable, prioritizing signals tied to critical flows. Avoid vanity metrics with no associated operational decision, and set thresholds only with reasonable operational criteria.

When should I escalate an observability proposal to the CTO?

Escalate when a proposal requires significant new infrastructure or a stack change, conflicts with security or compliance constraints, or introduces cross-cutting monitoring that changes how the system is operated.

What are common observability anti-patterns to avoid?

Avoid imposing enterprise observability without a roadmap, measuring everything while understanding nothing, using dashboards as a substitute for runbooks, logging sensitive data for debugging convenience, and proposing tooling outside the approved baseline.