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

Alert - Custom field #75

Closed
JulienChampseix opened this issue Dec 2, 2015 · 5 comments
Closed

Alert - Custom field #75

JulienChampseix opened this issue Dec 2, 2015 · 5 comments

Comments

@JulienChampseix
Copy link

That will be good if inside the mail sent over alerting system we could include an content like an URL which could contain procedure.

By this way we could a mail template having:

  • metrics impacted by the alert
  • current threshold exceed
  • URL procedure linked to this alert

Just an idea when it's an support team receiving alert. By this way they will know which metrics impacted and whichaction required following the URL procedire included into the alert for resolve the problem ;-)

Thanks for your feedback.

Julien.

@schmurfy
Copy link

I have not tried but judging by the documentation the email body is a dump of the JSON data, if that's the case there should be a method like message() to force a specific user template instead, it would be a nice way to solve this issue.

I just started to play around with kapacitor but that is clearly something I will need when I try to really use it, having a JSON dump in the body does not seems hat useful for real world use, if you are going to send the alert to another program http would be far easier.

@nathanielc
Copy link
Contributor

The alert node supports methods like .id() and .message() that define templates for a unique id for the alert as well as the single line message. We could add .details() method that defines a template for more detail which can be used by the email handler.

@JulienChampseix
Copy link
Author

@nathanielc that will be indeed usefull to have .details() method

@aabouzaid
Copy link

Hmmm I'm not sure, but isn't this issue about creating a "Custom field" in general?

Now there is details field, but what if a field needs to be added? (as same as the level of details field, not inside it).

I think this is not covered here. Should I open a new issue?

@nathanielc
Copy link
Contributor

@aabouzaid Yes, if you have a use case in mind please open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants