tsuga-metric-naming-fix

To fix metric names for OpenTelemetry conventions, you need to convert underscore notation to dots, remove service or environment prefixes, and strip unit suffixes like _ms or _bytes from your instrumentation code. This Skill automates that renaming process across your codebase.

Broken dashboard alerts often occur when metric names violate OTel naming conventions by using underscores or embedding environment prefixes. This Skill identifies these violations, checks downstream monitors and dashboards for references, and proposes a safe rename table before editing.

The best way to find non-compliant metric instrumentation call sites is to inspect the codebase using Tsuga CLI commands. This Skill locates exact file paths and line numbers for metric naming violations, providing evidence-based change planning before you apply any code refactors.

You cannot automatically rename metrics without risk, because existing monitors and dashboards may reference the old names. This Skill uses Tsuga CLI to check downstream impact and requires explicit user confirmation before applying any file edits to ensure safety.

Yes, the OTel metric renaming process skips metrics that have no aggregation data. This safe mutation workflow ensures the Skill only proposes renaming changes for active metrics that have clear evidence and downstream impact analysis.