Bug #46681 agent log has 'critical' msg that is not critical: starting task 2 for mysql::..

• Submitted: 12 Aug 2009 20:42
• Modified: 14 Jan 2010 14:50
• Reporter: Carsten Segieth
• Status: Closed
• Category: MySQL Enterprise Monitor: Agent
• Severity: S3 (Non-critical)
• Version: 2.1.0.1093
• OS: Any
• Assigned to: Jan Kneschke
• CPU Architecture: Any

[12 Aug 2009 20:42] Carsten Segieth

Description:
In the agent log there is a 'critical' message

   starting task 2 for mysql::server[2189a852-019b-49a5-9cab-294d1115b474]

where 'critical' is not needed as mode. It's a status message 'only'.

How to repeat:
- start agent and check log

Suggested fix:
- reduce logging level, e.g. to 'message'

[14 Aug 2009 18:47] Enterprise Tools JIRA Robot

Gary Whizin writes: 
log entry occurs once per agent startup

[18 Aug 2009 10:42] Enterprise Tools JIRA Robot

Mark Leith writes: 
Patch pushed:

1490 Mark Leith	2009-08-18
     Bug#46681 / EM-3517 - only log starting task messages at message level instead of debug level

   modified:
     plugins/agent/network-io.c

[17 Nov 2009 19:57] Enterprise Tools JIRA Robot

Keith Russell writes: 
Patch installed in versions => 2.1.1.1108.

[17 Dec 2009 20:52] Enterprise Tools JIRA Robot

Carsten Segieth writes: 
tested OK also in current 2.1.1.1114 build

[14 Jan 2010 14:50] MC Brown

A note has been added to the 2.1.1 changelog: 

 The task message for a given server within the agent would be logged at the incorrect level. Messages are now logged at the message level.