skills.rest
TrogonStack
TrogonStackOFFICIAL
Explore all skills by this author →
GitHub

otel-name-metric

Validate and standardize OpenTelemetry metric names and attribute structures.

10|2|Updated Feb 9, 2026
Search Tags:#metrics#observability#instrumentation#telemetry#opentelemetry#naming
One-click install
npx skills add https://github.com/TrogonStack/agentskills --skill otel-name-metric
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: otel-name-metric
Source: https://github.com/TrogonStack/agentskills/tree/main/plugins/trogonstack-otel/skills/otel-name-metric
Command: npx skills add https://github.com/TrogonStack/agentskills --skill otel-name-metric

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves inconsistencies in metric naming, ensuring that your telemetry data adheres to OpenTelemetry semantic conventions and remains queryable across your entire infrastructure.

Core Features & Use Cases

  • Naming Validation: Automatically checks metric names for correct dot-delimited snake_case, proper pluralization, and forbidden suffixes like _total.
  • Attribute Guidance: Provides clear rules on where to place dimensions (name vs. resource vs. attribute) to prevent cardinality explosions.
  • Instrument Selection: Offers a decision tree to help you choose between Counters, Gauges, and Histograms based on your measurement needs.

Quick Start

Use the otel-name-metric skill to review my proposed metric name system.cpu.usage_total and suggest corrections based on semantic conventions.

Frequently Asked Questions about otel-name-metric

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

FAQPage Schema
How do I validate OpenTelemetry metric names against semantic conventions?▼

To validate OpenTelemetry metric names, ensure they use dot-delimited snake_case, correct pluralization, and remove forbidden suffixes like _total. This standardizes telemetry data for consistent querying across your observability infrastructure.

What is the best way to prevent cardinality explosions in OpenTelemetry attributes?▼

Prevent cardinality explosions by applying strict rules for dimension placement across metric name, resource, and attribute fields. Properly structuring these dimensions ensures your telemetry data remains queryable and efficient.

How do I choose between OpenTelemetry Counters, Gauges, and Histograms?▼

Choose between OpenTelemetry Counters, Gauges, and Histograms by using a decision tree based on your specific measurement needs. This instrument selection best practice ensures accurate telemetry instrumentation and data collection.

Does OpenTelemetry instrumentation require UCUM unit standards for metrics?▼

OpenTelemetry instrumentation requires UCUM unit standards for metrics to ensure compliance with official semantic conventions. Applying these standards guarantees your measurement data remains consistent and queryable across systems.

Why does my OpenTelemetry metric name system.cpu.usage_total fail semantic convention checks?▼

Your OpenTelemetry metric name fails semantic convention checks because it uses the forbidden _total suffix. Standardizing metric names requires removing such suffixes and applying correct dot-delimited snake_case formatting.

Related Skills

Explore More Software Engineering Skills→
razorpayrazorpay
31

baseline-monitoring

Define and enforce universal baseline metrics for Razorpay Go services.

Official
Intermediate
nguyenpv1980-wqnguyenpv1980-wq
2

observability-operator

Instrument services with structured telemetry and validated alerting.

Community
Advanced
DevelopersGlobalDevelopersGlobal
65

observability

Implement structured logging, distributed tracing, and alerting with OpenTelemetry.

Official
Advanced
adrielpadrielp
20

otel_semantic_conventions

Enforce OpenTelemetry semantic conventions for telemetry attribute naming and placement.

Community
Advanced