observability-architect

Instrument structured logs, metrics, and traces with correlation rules.

3|Updated Feb 26, 2026

Search Tags:#logging #metrics #observability #tracing #opentelemetry #redaction #correlation

Ready to run

npx skills add https://github.com/ralvarezdev/ralvaskills --skill observability-architect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-architect
Source: https://github.com/ralvarezdev/ralvaskills/tree/main/skills/infra/observability-architect
Command: npx skills add https://github.com/ralvarezdev/ralvaskills --skill observability-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Instrumentation for application signals: logs, metrics, and traces, with strict correlation and naming rules to enable fast debugging and reliable dashboards.

Core Features & Use Cases

Enforces standardized signal emission (JSON logs, Prometheus metrics, OpenTelemetry traces) and cross-skill alignment with grafana-architect.
Provides guidance for signal naming, data redaction, sampling, and cross-service correlation to support reliable observability and incident response.
Use Case: When deploying a new service, wire up logs, metrics, and traces following the architecture guidelines to enable end-to-end visibility.

Quick Start

Instrument your service to emit structured logs, metrics, and traces that correlate via trace_id across signals.

Frequently Asked Questions about observability-architect

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

FAQPage Schema

How do I implement end-to-end observability across multiple services?▼

End-to-end observability is implemented by instrumenting services to emit structured JSON logs, Prometheus metrics, and OpenTelemetry traces correlated via a shared trace_id across all signals.

What is the best way to correlate logs, metrics, and traces for faster debugging?▼

Correlate logs, metrics, and traces by enforcing standardized signal naming and applying strict correlation rules using trace_id, ensuring all signals can be cross-referenced during incident response.

How do I enforce structured logging and redaction policies in production applications?▼

Enforce structured logging and redaction by applying standardized JSON log emission rules and data redaction policies across production services to secure sensitive information while maintaining searchable logs.

Does this observability guidance work with multi-language application stacks?▼

Yes, the observability instrumentation is designed to be applied across multi-language stacks, enforcing consistent signal naming, sampling, and cross-service correlation regardless of the programming language.

What do I need to set up OpenTelemetry tracing and Prometheus metrics for a new service?▼

To set up tracing and metrics for a new service, you wire up OpenTelemetry traces and Prometheus metrics following architecture guidelines that enforce standardized signal emission and cross-skill alignment.