Bug #44262 The length of the data recovery period for an agent should be configurable
Submitted: 14 Apr 2009 13:12 Modified: 18 Mar 2010 9:02
Reporter: Roger David Nay Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Kay Roepke CPU Architecture:Any

[14 Apr 2009 13:12] Roger David Nay 
Description:
The length of the data recovery period for an agent in case of a monitor restart is not configurable. The default of 10 minutes is fine for a server restart but needs to be configurable for longer times in case of server maintenance for example.

How to repeat:
N/A

Suggested fix:
Configurable ideally from the dashboard, but acceptable the configuration file as well.
[2 Dec 2009 22:13] Enterprise Tools JIRA Robot 
Keith Russell writes: 
Patch installed in versions => 2.2.0.1563.
[15 Jan 2010 18:13] Enterprise Tools JIRA Robot 
Diego Medina writes: 
Hard to tell that the new option works, because I still see gaps on the graph.

How to repeat:

1- Install and start the service manager
2- Install and start the agent
3- Wait until you see the server on the dashboard.
4- stop the dashboard (and mysqld repo) , wait  120 seconds and start the repo and dahboard
5- look at the graphs on the dashboard, it will take a while to see data, and eventually you will se the gaps
[15 Jan 2010 18:14] Enterprise Tools JIRA Robot 
Diego Medina writes: 
Graph with gap
[15 Jan 2010 18:14] Enterprise Tools JIRA Robot 


Attachment: 10265_EM-3251.png (image/png, text), 30.43 KiB.
[15 Jan 2010 18:30] Enterprise Tools JIRA Robot 
Diego Medina writes: 
repo dump
[15 Jan 2010 18:30] Enterprise Tools JIRA Robot 


Attachment: 10266_EM-3251.sql.gz (application/x-gtar, text), 102.46 KiB.
[17 Mar 2010 20:35] Enterprise Tools JIRA Robot 
Diego Medina writes: 
Verified fixed on  	2.2.0.1641
[18 Mar 2010 9:02] MC Brown 
A note has been added to the 2.2.0 changelog: 

        When a &merlin_agent; is disconnected from &merlin_server;,                                                                                         
        the agent would keep 10 minutes of information by default,                                                                                          
        that would then be sent to the server when the agent                                                                                                
        reconnected. Any data older than 10 minutes would be lost. You                                                                                      
        can now configure the backlog timeout by using                                                                                                      
        the <option>agent-backlog-timeout</option> to specify the                                                                                           
        amount of time that data will be kept. For more information,                                                                                        
        see                                                                                                                                                 
        <xref linkend="option_mysql-monitor-agent_agent-backlog-timeout"/>.