MySQL Bugs: #46822: Add smaller than 1 week period to purge logs/historical data in MEM

Bug #46822	Add smaller than 1 week period to purge logs/historical data in MEM
Submitted:	20 Aug 2009 9:02	Modified:	6 Nov 2009 16:21
Reporter:	Victoria Reznichenko	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S4 (Feature request)
Version:	any	OS:	Any
Assigned to:	Josh Sled	CPU Architecture:	Any

Description:
Currently the smallest period to purge logs/historical data is 1 week.
It would be good to be able to set smaller period.

Currently there is workaround to set it manually, for example using link like below:

http://localhost:18080/main?command=set_property&property=quan.lifespan&value=1

however it is always better to be able to do it via UI.

How to repeat:
1. Install MEM
2. Check settings tab

Sloan Childers writes: 
Need to investigate if this is an easy UI tweak (ie. no backend work required) to add support for shorter purge intervals - if so we can leave as a 2.1.x maintenance thing.

Josh Sled writes: 
revno: 7468
revision-id: jsled@asynchronous.org-20090911135735-0619bwljc8ydnqyi
parent: merlin@dl380-g5-a.mysql.com-20090909174905-52uhlwuoc7lbiocc
committer: Josh Sled <jsled@asynchronous.org>
branch nick: 2.1-bugs
timestamp: Fri 2009-09-11 09:57:35 -0400
message:
  EM-3535, Bug#46822: add sub-1-week purge options; factor common code out of 4 different UI classes.

Keith Russell writes: 
Patch installed in versions => 2.1.1.1104 & versions => 2.2.0.1501.

Diego Medina writes: 
Verified fixed on 2.1.1.1104  and 2.2.0.1515

An entry has been added to the 2.2.0 and 2.1.1 changelogs:

The smallest purge log time interval that could be set in the Dashboard was one week. MySQL Enterprise Monitor was changed to allow setting the smallest purge log time interval to one day.