Bug #29657 Allow per-advisor blackout options

• Submitted: 9 Jul 2007 18:58
• Modified: 9 Jan 2015 14:14
• Reporter: Todd Farmer (OCA)
• Status: Won't fix
• Category: MySQL Enterprise Monitor: Server
• Severity: S4 (Feature request)
• Version: 2.2
• OS: Any
• Assigned to: Assigned Account
• CPU Architecture: Any

[9 Jul 2007 18:58] Todd Farmer

Description:
As of MNMAS 1.1, users are able to use blackout functionality to suppress alerts during specific periods.  The use case is described, "Database servers require regular maintenance and during these periods you may wish to stop Service Agents from reporting their findings."  For many maintenance operations, only specific advisors should be affected (for example, CPU utilization may be high during nightly batch processing), but there is no ability currently to blackout only certain advisors.  Turning off all advisors is too coarse-grained of a solution; the server might die without a triggered alert during the maintenance period.

How to repeat:
N/A

Suggested fix:
Please add ability to disable alerts for specific advisors during blackout period.

[13 Nov 2014 8:50] Daniël van Eeden

Today I had to do an ALTER TABLE on a slave which would cause a big spike in slave delay. I couldn't put the server on blackout as that would also cause other alerts to stop. Temporarily changing advisor settings would be risky as one could easily forget tho change them back to the correct settings.

As a partly workaround one could add a note to the server on the instances screen which could be used to let others know one is working on the server. This could be made to work a bit better if the note was sent in email and snmp alerts.