What is instrumentation planning?

Instrumentation planning is the process of strategically defining which metrics, spans, and logs to collect before writing code, ensuring the resulting telemetry is useful, affordable, and consistent.

How does this skill help manage monitoring costs?

It provides frameworks for cardinality budgeting and reduction techniques, helping you identify and eliminate 'metric explosions' that lead to high cloud monitoring bills.

When is the best time to use the Instrumentation Planning skill?

It is best used during the design phase of a new service, when reviewing existing telemetry for a migration, or when troubleshooting high observability costs.

Does this skill support OpenTelemetry standards?

Yes, the naming conventions and span structures provided are designed to align with OpenTelemetry and modern observability best practices.

Instrumentation Planner

Name: Instrumentation Planner
Author: melodic-software

bymelodic-software

•

分析与监控

Architects comprehensive application instrumentation strategies covering naming conventions, cardinality management, and observability budgets.

关于

The Instrumentation Planning skill provides a strategic framework for designing application observability before implementation begins. It guides developers through defining what to instrument across multiple layers—from automatic library metrics to critical business transactions—while establishing strict naming conventions and managing the risks of high-cardinality data. By using this skill, teams can proactively control monitoring costs, minimize performance overhead, and ensure that their telemetry data is actionable, consistent, and structured for long-term system health.

主要功能

Standardized naming conventions for metrics, spans, and log fields following industry best practices
5 GitHub stars
Proactive cardinality budgeting and reduction techniques to prevent cost explosions
Detailed cost and performance impact estimation for telemetry data
Multi-layered strategy framework for auto, business, and diagnostic telemetry
Instrumentation decision matrix to balance business value against performance impact

使用场景

Designing the observability architecture for a new microservice or distributed system
Standardizing metric and span naming conventions across a multi-team engineering organization
Identifying and mitigating high-cardinality metrics that are inflating monitoring bills

关于

主要功能

Standardized naming conventions for metrics, spans, and log fields following industry best practices
5 GitHub stars
Proactive cardinality budgeting and reduction techniques to prevent cost explosions
Detailed cost and performance impact estimation for telemetry data
Multi-layered strategy framework for auto, business, and diagnostic telemetry
Instrumentation decision matrix to balance business value against performance impact

使用场景

Designing the observability architecture for a new microservice or distributed system
Standardizing metric and span naming conventions across a multi-team engineering organization
Identifying and mitigating high-cardinality metrics that are inflating monitoring bills