| Bug #37465 | Higher Control over notification groups | ||
|---|---|---|---|
| Submitted: | 17 Jun 2008 22:21 | Modified: | 9 Jan 2015 10:02 |
| Reporter: | Adam Dixon | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Web | Severity: | S4 (Feature request) |
| Version: | 1.x,2.0 | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[17 Jun 2008 22:21]
Adam Dixon
[2 Oct 2008 16:33]
Josh Sled
> There's also been talk about doing little within our own app but instead > integrating nicely with existing notification systems. Any thoughts? Sure! This should get into the product roadmap, maybe? It'd be good to know what existing monitoring/notification systems (nagios, ganglia, &c.) are in place with our customers so we can figure out what/how to deliver notifications (or alerts) to them. Otherwise, I don't know about general workflow mumble … Notification groups could be defined and parametrized by the time of day, day of week, level of alert and maybe type of server/host involved (send mysql alerts to one group, machine CPU/disk alerts to another, &c.) At least, this is what I recall nagios easily allows. We should probably try to have basic feature parity with other solutions if we're either going to do it ourselves or integrate with others.
[24 Jun 2009 21:35]
Enterprise Tools JIRA Robot
Josh Sled writes: See EM-242.
