observability-setup

Define and enforce OpenTelemetry-based instrumentation patterns for traces, metrics, and logs.

15|5|Updated May 17, 2026
One-click install
npx skills add https://github.com/cropsgg/skills --skill observability-setup-cropsgg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-setup
Source: https://github.com/cropsgg/skills/tree/main/skills/productivity/observability-setup
Command: npx skills add https://github.com/cropsgg/skills --skill observability-setup-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides engineering teams to establish a consistent observability baseline by defining traces, metrics, logs, and query patterns aligned with OpenTelemetry-oriented standards.

Core Features & Use Cases

  • Standardized instrumentation: Establish traces, metrics, and logs that are consistent across services.
  • Queryable dashboards: Predefined query templates for SLOs, latency, error rates, and dependency graphs.
  • Onboarding and rollout: Quick-start templates for new services and incident debugging.

Quick Start

Configure a new service to instrument traces, metrics, and logs using the provided OpenTelemetry-aligned guidelines and dashboards.

Frequently Asked Questions about observability-setup

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

FAQPage Schema
How do I set up OpenTelemetry instrumentation for traces, metrics, and logs?

Apply OpenTelemetry-based instrumentation patterns to establish consistent traces, metrics, and logs across services. This approach enforces standardized signal naming and semantic attributes for reliable observability across development, staging, and production.

How do I create observability dashboards for SLOs and latency tracking?

Create observability dashboards using predefined query templates for SLOs, latency, error rates, and dependency graphs. These templates leverage standardized semantic attributes to generate queryable dashboards for incident debugging and monitoring.

What is the best way to standardize observability signals across existing services?

Standardize observability signals by enforcing OpenTelemetry-based instrumentation patterns that define consistent trace, metric, and log naming. This creates a unified observability baseline with standardized semantic attributes across all existing services.

Can I use OpenTelemetry instrumentation for new service onboarding and rollout?

Yes, OpenTelemetry instrumentation supports new service onboarding through quick-start templates. These templates provide rollout and validation guidance to ensure consistent traces, metrics, and logs from development through production environments.

Does OpenTelemetry instrumentation work across development, staging, and production environments?

OpenTelemetry instrumentation applies to development, staging, and production environments. It enforces standardized signal naming and semantic attributes across all stages to maintain consistent observability signals and queryable dashboards.