Bug #35540 Black-out functionality for advisor scheduling.

• Submitted: 25 Mar 2008 0:51
• Modified: 25 Mar 2008 11:16
• Reporter: Mikiya Okuno
• Status: Not a Bug
• Category: MySQL Enterprise Monitor: Advisors/Rules
• Severity: S4 (Feature request)
• Version: 1.3.0.8939
• OS: Any
• CPU Architecture: Any

[25 Mar 2008 0:51] Mikiya Okuno

Description:
During running backup, the server load becomes very high and some advisors such as "CPU Usage Excessive" reach their thresholds very easily, and the events will not fire again unless they're removed once. Events should not be triggered on such CPU high usage spikes.

It is reasonable solution that the Service Advisor can be disabled only some certain range of time, e.g. during backup between 0am and 3am.

How to repeat:
nada

Suggested fix:
Currently, Advisors can be scheduled using only their frequency. Time range should be specified as well.

[25 Mar 2008 11:16] Mark Leith

This already exists, see section 7.6 of the documentation:

7.6. Scriptable Advisor Blackout Periods

Database servers require regular maintenance and during these periods you may wish to stop Service Agents from reporting their findings. During a blackout period rules are not evaluated and notifications are put on hold but Service Agents continue to collect data . In this respect blacked-out rules differ from disabled rules; data continues to be collected and stored in the repository.

Blackout periods are enabled by entering the following URL into the address bar of your browser, substituting the appropriate hostname, port and server name:

http://localhost:18080/merlin/rest?command=blackout&server_name=SuSE:3306&blackout_state=t...