Skip to content

docs: Document brace syntax for dimension names with spaces in alert#22984

Draft
nedi-app[bot] wants to merge 1 commit into
masterfrom
docs/docs-alerts-dimension-with-spaces-as-variable
Draft

docs: Document brace syntax for dimension names with spaces in alert#22984
nedi-app[bot] wants to merge 1 commit into
masterfrom
docs/docs-alerts-dimension-with-spaces-as-variable

Conversation

@nedi-app

@nedi-app nedi-app Bot commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

Summary

Document brace syntax for dimension names with spaces in alert expressions. Files changed: src/health/REFERENCE.md.

User Request

How to use a dimension as a variable in an alert if the dimension has spaces. Eg: Has Number..

Prompt (English)

How to reference a dimension with spaces (e.g. "Has Number..") as a variable in a Netdata alert expression

Reason for Change

This change applies the specific user request using repository-truth evidence from the audit execution workspace.


Summary by cubic

Documented how to reference dimensions with spaces in alert expressions using the ${...} brace syntax. Added a ${Has Number} example for calc/warn/crit and noted that $Has Number won’t resolve; also mentions the same rule for hyphenated names (e.g., Prometheus chart IDs).

Written for commit 5ffcfdc. Summary will update on new commits.

Review in cubic

… of src/health/REFERENCE.md explaining that dimension names containing spaces must be referenced with the ${...} brace form in calc/warn/crit expressions, with a concrete ${Has Number} example and a cross-reference to the Prometheus section that uses the same brace rule for hyphenated chart IDs.
@nedi-app nedi-app Bot added the nedi-audit PRs created by the nedi-audit pipeline label Jul 5, 2026
@sonarqubecloud

sonarqubecloud Bot commented Jul 5, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/docs area/health nedi-audit PRs created by the nedi-audit pipeline

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants