skills.rest
shafibabar
shafibabarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

metrics-instrumentation-plan

Define instrumentation plans mapping product, business, and delivery metrics to sources.

1|Updated Jun 20, 2026
Search Tags:#analytics#metrics#observability#instrumentation#traceability#dora
One-click install
npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill metrics-instrumentation-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: metrics-instrumentation-plan
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/metrics-instrumentation-plan
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill metrics-instrumentation-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves the confusion between system, product, and delivery metrics, ensuring that every metric is correctly owned, sourced, and tied to a specific business decision or OKR.

Core Features & Use Cases

  • Metric Categorization: Clearly distinguishes between system health (OTel), product value (Domain Events), and delivery performance (DORA).
  • Event-to-Metric Traceability: Provides a structured framework to map metrics back to their raw data sources, preventing tribal knowledge and untraced dashboard numbers.
  • Use Case: Use this to define the instrumentation plan for a new service, ensuring that DORA metrics are sourced from CI/CD pipelines rather than application telemetry.

Quick Start

Use the metrics-instrumentation-plan skill to generate a new instrumentation definition table for the current service.

Frequently Asked Questions about metrics-instrumentation-plan

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

FAQPage Schema
What is event-to-metric traceability and why do I need it for observability?▼

Distinguishing delivery metrics from system metrics ensures DORA performance data is sourced from CI/CD pipelines, while system health relies on OpenTelemetry. This separation prevents metric confusion and ensures accurate ownership.

How do I create an instrumentation plan for a new service?▼

Generate an instrumentation definition table for the new service to map product, business, and delivery metrics to their respective sources. This establishes a structured framework aligning observability and performance tracking.

Can I use this to align product and business metrics with DORA standards?▼

Yes, the plan standardizes DORA delivery metrics while categorizing them alongside product value and system health. It applies to data and platform engineering workflows to establish comprehensive observability and performance tracking.

What's the best way to map dashboard consumption to raw data sources?▼

Apply a structured framework to map metrics back to their raw data sources, preventing tribal knowledge and untraced dashboard numbers. This ensures every metric is correctly owned and sourced for specific business decisions.

When should I source DORA metrics from CI/CD pipelines instead of application telemetry?▼

DORA delivery performance metrics should be sourced from CI/CD pipelines rather than application telemetry to accurately reflect deployment frequency and lead time. This categorizes delivery metrics separately from system health and product value.

Related Skills

Explore More Data & Analytics Skills→
balic-AI-ML-R-D-Resourcesbalic-AI-ML-R-D-Resources

security-audit-context-building

Map architecture, trust boundaries, and data flows for security audit scoping.

Official
Advanced
devmuslimdevmuslim

delivery-kpis

Define and track DORA and flow metrics for product delivery teams.

Community
Intermediate
coralogixcoralogix
4

opentelemetry-ottl

Write and debug OTTL statements for OpenTelemetry Collector pipelines.

Official
Advanced
linguistic76linguistic76
2

prometheus-grafana

Instrument Prometheus metrics and create Grafana dashboards with PromQL queries.

Community
Advanced