Bug #83228 send log level in ndb_mgmd syslog logging
Submitted: 30 Sep 2016 18:08
Reporter: Lucas Jackson Email Updates:
Status: Open Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S4 (Feature request)
Version:7.4.12 OS:Linux
Assigned to: CPU Architecture:Any
Tags: syslog logging ndb_mgmd

[30 Sep 2016 18:08] Lucas Jackson 
Description:
Not sure if this is an S4 or not as I just started using syslog logging for ndb_mgmd. Feel free to reclassify as S3 if this is not expected behaviour.

I'm logging ndb_mgmd to syslog with:
LogDestination=SYSLOG:facility=local7

Backend is rsyslog

Syslog log entries look like:
NDB[30169]: [MgmtSrvr] Alloc node id 2 failed with error code 1703, will retry

While a comparable ndb_X_cluster.log log entry looks like:
2016-09-29 07:17:19 [MgmtSrvr] INFO     -- Alloc node id 2 failed with error code 1703, will retry

Would be nice to see the log level in the syslog log entries, if this is not a bug. Thanks.

How to repeat:

[NDB_MGMD]
LogDestination=SYSLOG:facility=local7

Suggested fix:
Add log level to log entries