Bug #35540 Black-out functionality for advisor scheduling.
| Submitted: | 25 Mar 2008 0:51 | Modified: | 25 Mar 2008 11:16 |
|---|---|---|---|
| Reporter: | Mikiya Okuno | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Advisors/Rules | Severity: | S4 (Feature request) |
| Version: | 1.3.0.8939 | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[25 Mar 2008 0:51]
Mikiya Okuno
[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...
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.