Bug #45884 | log version on agent start up and possibly shut down | ||
---|---|---|---|
Submitted: | 1 Jul 2009 16:00 | Modified: | 21 Jul 2009 9:37 |
Reporter: | Marcos Palacios | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Agent | Severity: | S3 (Non-critical) |
Version: | 2.1.0.1067 | OS: | Any |
Assigned to: | Kay Roepke | CPU Architecture: | Any |
[1 Jul 2009 16:00]
Marcos Palacios
[1 Jul 2009 16:16]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Comment from Kay: The agent already logs it's version number on startup, although not on the default log level. I'm opposed to also log it on shutdown, since even rotating the logs should not remove any logs. For the agent the --version flag will show the version number: ./bin/mysql-monitor-agent --version
[1 Jul 2009 16:16]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Comment from Kay: The agent already logs it's version number on startup, although not on the default log level. I'm opposed to also log it on shutdown, since even rotating the logs should not remove any logs. For the agent the --version flag will show the version number: ./bin/mysql-monitor-agent --version
[1 Jul 2009 16:42]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Comments: This feature is available with "log-level=debug" in <inst-dir>/etc/mysql-monitor-agent.ini. It shows these lines: 2009-07-01 11:33:43: (message) mysql-proxy 0.7.0 started 2009-07-01 11:33:43: (message) MySQL Monitor Agent 2.1.0.1067 started. Resolution: Verified fixed in agent build 2.1.0.1067.
[1 Jul 2009 16:42]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Comments: This feature is available with "log-level=debug" in <inst-dir>/etc/mysql-monitor-agent.ini. It shows these lines: 2009-07-01 11:33:43: (message) mysql-proxy 0.7.0 started 2009-07-01 11:33:43: (message) MySQL Monitor Agent 2.1.0.1067 started. Resolution: Verified fixed in agent build 2.1.0.1067.
[2 Jul 2009 15:33]
Kay Roepke
The information is available on log level "message", in the service manager dashboard and from running mysql-monitor-agent --version. Per request it will be logged on log level "critical" at startup in the future.
[6 Jul 2009 21:58]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch applied in versions => 2.1.0.1074.
[7 Jul 2009 22:08]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Verified fixed in agent build 2.1.0.1074. 2009-07-07 16:55:08: (critical) MySQL Monitor Agent 2.1.0.1074 started.
[21 Jul 2009 9:37]
Tony Bedford
An entry has been added to the 2.1.0 changelog: The Agent did not write its version number to the log on startup or shutdown. The information is now available by setting log level “MESSAGE” in the Dashboard. It is also available when running the Agent from the command line with the command mysql-monitor-agent --version. The Agent also now logs its version number on startup if the log level is set to “CRITICAL”.