observability

Instrument logs, traces, and metrics with OpenTelemetry across code boundaries.

7|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/bricerising/enterprise-software-playbook --skill observability-bricerising
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/bricerising/enterprise-software-playbook/tree/main/skills/observability
Command: npx skills add https://github.com/bricerising/enterprise-software-playbook --skill observability-bricerising

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Observability instrumentation across code boundaries to standardize logs, traces, and metrics.

Core Features & Use Cases

  • Instrument logs, traces, and metrics consistently across services.
  • Define stable field contracts, dashboards, and alerts to enable rapid incident response.
  • Use OpenTelemetry or equivalent to collect, correlate, and visualize telemetry data across boundaries.

Quick Start

Configure your service to emit structured logs, traces, and metrics using OpenTelemetry.

Frequently Asked Questions about observability

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

FAQPage Schema
How do I standardize logs, traces, and metrics across multiple services?

To instrument observability for new code, apply stable field contracts and emit structured logs, traces, and metrics using OpenTelemetry. This enforces RED metrics and provides guidelines for building dashboards and runbooks to ensure reliable monitoring across code boundaries.

What is the best way to define stable field contracts for observability data?

You can use OpenTelemetry to collect, correlate, and visualize telemetry data across code boundaries. It serves as the core tool for instrumenting logs, traces, and metrics consistently, allowing you to standardize observability data and define stable field contracts.

How do I build dashboards and alerts for rapid incident response?

Build dashboards and alerts by instrumenting RED metrics and enforcing stable field contracts across your services. Using OpenTelemetry to standardize logs, traces, and metrics provides the necessary telemetry data to define guidelines for dashboards and runbooks, enabling rapid incident response.

Why do I need structured logs and traces for observability instrumentation?

Structured logs and traces are needed for observability instrumentation to standardize telemetry data across code boundaries. By defining stable field contracts and using OpenTelemetry, you ensure consistent collection and correlation of logs, traces, and metrics for reliable dashboards and alerts.