- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Trigger works but not sending alerts
- Labels:
-
Apache Flume
-
Cloudera Manager
Created on ‎10-29-2015 07:17 PM - edited ‎09-16-2022 02:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I created a trigger for a flume in cloudera manager, with a certain condition (Eps drops to < 5). Here is the condition:
SELECT event_put_success_rate_across_flume_channels WHERE entityName="flume" AND last(event_put_success_rate_across_flume_channels) <= 5.
It is triggering now as seen in the CM UI. However I was expecting it to also send alert by email, which it does not. I am getting alerts by email on other things but not the custom triggers. What am I missing in configuring my trigger/alert?
I restarted Flume, Alert Publisher and the CM service management as well. Anything else I am missing?
Thank you!
Created ‎02-12-2016 02:20 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, this is resolved. The problem was the alert threshold was set to send emails when a service enters a Bad state. However the trigger expression was "DO health:concerning"
Once I changed it to "DO health:bad" it worked. User mistake, again 😞
Created ‎12-28-2015 05:29 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having this problem, too. Have you found a solution?
Created ‎01-04-2016 08:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No 😞
Created ‎02-12-2016 02:20 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, this is resolved. The problem was the alert threshold was set to send emails when a service enters a Bad state. However the trigger expression was "DO health:concerning"
Once I changed it to "DO health:bad" it worked. User mistake, again 😞
Created ‎02-13-2016 04:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great to see that you resolved your issue. Feel free to mark your last comment as the solution in case it can assist others. 🙂
Cy Jervis, Manager, Community Program
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Created on ‎02-15-2016 09:31 AM - edited ‎02-15-2016 09:32 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just did, thank you.
