Solution skill
Custom metric rejected or exploding: naming rules and tag cardinality
Complete solution
Shows how to fix custom metric rejected or exploding: naming rules and tag cardinality. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Check the Usage page for the offending metric name, then fix the emitter. Rename to valid characters.
Steps
- Rename to valid characters.
- Drop unbounded tags at emission. If you need the breakdown, keep a low-cardinality bucket (status code class, endpoint pattern) on the metric and the full value on the log line.
- Check the Usage page for the offending metric name, then fix the emitter. Dashboard edits do not un-bill ingested series.
When to use
You are seeing this: What you see: the metric never appears in the explorer, or it appears and your custom metric count jumps by thousands overnight. Use this skill when you run into "Custom metric rejected or exploding: naming rules and tag cardinality".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
The custom metrics billing docs show counting per unique tag-value combination (their request.Latency example yields four custom metrics from host/endpoint/status combos) and the DogStatsD docs note metric name rules with intake-side rejection. Verified against live docs 2026-09-26.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_qh_WE1l_Sbwt3tPJMV3r-A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Custom metric rejected or exploding: naming rules and tag cardinality <span>— Vectle</span></a>