Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot use non-ascii characters in alert name #2255

Closed
bsd04 opened this Issue Dec 5, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@bsd04
Copy link

bsd04 commented Dec 5, 2016

What did you do?

Created alert rule with following name: ALERT LiigaLühike ...

What did you expect to see?

Checking test.rules
SUCCESS: 1 rules found

What did you see instead? Under which circumstances?

Checking test.rules
FAILED: parse error at line 1, char 13: unexpected character: 'ü'

Environment

Linux localhost.localdomain 3.10.0-514.el7.x86_64

  • System information:

Linux 3.10.0-514.el7.x86_64 x86_64

  • Prometheus version:

prometheus, version 1.3.1 (branch: master, revision: be47695)
build user: root@37f0aa346b26
build date: 20161104-20:24:03
go version: go1.7.3

  • Alertmanager version:

alertmanager, version 0.5.1 (branch: master, revision: 0ea1cac51e6a620ec09d053f0484b97932b5c902)
build user: root@fb407787b8bf
build date: 20161125-08:14:40
go version: go1.7.3

  • Prometheus configuration file:

not relevant

  • Alertmanager configuration file:

not relevant

  • Logs:

not relevant

@beorn7

This comment has been minimized.

Copy link
Member

beorn7 commented Dec 6, 2016

That's the intended behavior. An alert name is treated the same as a metric name in PromQL, see https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels for restrictions.

We should document that more clearly. I have filed prometheus/docs#636 for that.

@beorn7 beorn7 closed this Dec 6, 2016

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 24, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.