Bug #61035 | Event blackout not described completely in the documentation | ||
---|---|---|---|
Submitted: | 3 May 2011 7:31 | Modified: | 13 May 2011 18:07 |
Reporter: | Daniël van Eeden | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Documentation | Severity: | S3 (Non-critical) |
Version: | 2.3.3 | OS: | Any |
Assigned to: | John Russell | CPU Architecture: | Any |
[3 May 2011 7:31]
Daniël van Eeden
[3 May 2011 11:45]
Valeriy Kravchuk
Thank you for the documentation request. More details are needed here, http://dev.mysql.com/doc/mysql-monitor/2.3/en/mem-managing-servers.html, it seems.
[3 May 2011 15:19]
Marcos Palacios
In the section: "G.2. Changes in MySQL Enterprise Monitor 2.3.2 (1 March 2011)" at: http://dev.mysql.com/doc/mysql-monitor/2.3/en/mem-news-2-3-2.html we have (in the last entry): "The Manage Servers page now has a menu option [Enable | disable] event blackout. You can set up blackout periods through the Dashboard in addition to scripting them through the REST API. (Bug #34186)"
[13 May 2011 18:07]
John Russell
Added to 2.3 doc: Use the [Enable | disable] event blackout control to turn blackout periods on and off. The server name is greyed out while the blackout period is in effect. Only event reporting is affected; query analysis continues during the blackout period. and an xref to the "Managing Servers" section from the changelog.