observability-pillars-integration
CommunityLink metrics, logs, and traces in one flow
Authorohsonerdy
Version1.0.0
Installs0
System Documentation
What problem does it solve?
This skill fixes siloed observability setups where metrics, logs, and traces exist but cannot be composed during incidents, forcing responders to manually correlate data across tools.
Core Features & Use Cases
- Correlation-first integration guidance: Defines the required ID primitives (trace ID, span ID, service identity, environment/region) and explains how they must propagate across boundaries.
- Cardinality and volume discipline: Establishes safe rules for metric labels, log fields, sampling, and budget guardrails to prevent backend cost blowups.
- Practical remediation and verification: Provides an incremental rollout sequence (traceālogs via trace ID, metrics exemplars, deep-linking, shared dashboards) plus integration tests to prove end-to-end composition.
Quick Start
Use the observability-pillars-integration skill to design an end-to-end plan that makes trace IDs appear in logs, enables metric exemplars for trace pivoting, and validates the full cross-pillar flow with a synthetic request integration test.
Dependency Matrix
Required Modules
None requiredComponents
Standard packageš» Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: observability-pillars-integration Download link: https://github.com/ohsonerdy/openclaw-frontier-stack/archive/main.zip#observability-pillars-integration Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.