observability-baseline

Define structured logging, metrics, and tracing conventions for codebases.

6|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/vibbs/company-os --skill observability-baseline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-baseline
Source: https://github.com/vibbs/company-os/tree/main/.claude/skills/observability-baseline
Command: npx skills add https://github.com/vibbs/company-os --skill observability-baseline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill ensures that all services in a codebase generate consistent, queryable telemetry data, making it easier to monitor, debug, and alert on system behavior.

Core Features & Use Cases

  • Structured Logging: Defines required fields and formats for logs (e.g., request_id, level, message).
  • Metrics Conventions: Establishes naming schemes and standard metrics for application performance.
  • Tracing Standards: Outlines conventions for distributed tracing to understand request flows across services.
  • Use Case: When setting up a new microservice, use this Skill to define and document its logging, metrics, and tracing standards, ensuring it integrates seamlessly with the existing observability stack.

Quick Start

Use the observability-baseline skill to define structured logging conventions for the application.

Frequently Asked Questions about observability-baseline

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

FAQPage Schema
How do I standardize structured logging and metrics across a microservice codebase?

Standardize structured logging and metrics by establishing baseline conventions for required log fields and metric naming schemes. This ensures all services generate consistent, queryable telemetry data for monitoring and debugging.

What conventions are needed for distributed tracing to understand request flows?

Distributed tracing requires defined span conventions to track request flows across services. Establishing these tracing standards ensures consistent telemetry data for understanding system behavior and request paths.

Can I use this to define SLO-aligned alerting strategies for application performance?

Yes, you can define SLO-aligned alerting strategies for application performance. The approach establishes standard metrics and conventions to ensure alerts reliably reflect system behavior and service objectives.

What's the best way to ensure consistent queryable telemetry data in a new microservice?

The best way to ensure consistent queryable telemetry data is to define provider-specific patterns, required log fields, and tracing span conventions before deployment. This baseline integration makes monitoring and debugging reliable.

Why does inconsistent telemetry data make monitoring and debugging difficult?

Inconsistent telemetry data makes monitoring difficult because undefined log fields and unstandardized metrics prevent reliable querying. Establishing baseline conventions for structured logging and tracing solves this by ensuring data uniformity.