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

Frendly alert names? #2407

Closed
danisabad opened this Issue Feb 8, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@danisabad
Copy link

danisabad commented Feb 8, 2017

Hello.

Is it possible to give more human readable names to alerts? It would be nice to have spaces and other symbols like (,),[,],",'. Now all these gives parse error at line X, char X: unexpected string X.

Now best I can think of is, for example, 'File_system_space_available_percentage' or 'FileSystemSpaceAvailablePercentage' - which obviously isn't that convenient.

  • Prometheus version:
prometheus, version 1.5.0 (branch: master, revision: d840f2c400629a846b210cf58d65b9fbae0f1d5c)
  build user:       root@a04ed5b536e3
  build date:       20170123-13:56:24
  go version:       go1.7.4
  • Logs:
time="2017-02-08T11:45:17+01:00" level=error msg="Failed to apply configuration: error loading rules, previous rule set restored: error parsing sample.rule: parse error at line 18, char 8: unexpected string \"\\\"Filesystem Space\"... in alert statement, expected identifier" source="main.go:275"
@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Feb 8, 2017

There's no plans to change the limitations on alert names. Longer names would be harder to read on devices such as pagers where space is limited.

You can add more information using annotations.

@juliusv

This comment has been minimized.

Copy link
Member

juliusv commented Feb 13, 2017

Closing as there are no plans to change this.

@juliusv juliusv closed this Feb 13, 2017

@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.