Event Reports Generated in NDB Cluster Table 23.53 Cluster log categories, with default threshold setting Category Default threshold (All data nodes) STARTUP 7 SHUTDOWN 7 STATISTICS 7 CHECKPOINT 7 NODERESTART 7 CONNECTION 7 ERROR 15 INFO 7 Severity Level Value Severity Description 1 ALERT A condition that should be corrected immediately, such as a corrupted system database 2 CRITICAL Critical conditions, such as device errors or insufficient resources 3 ERROR Conditions that should be corrected, such as configuration errors 4 WARNING Conditions that are not errors, but that might require special handling 5 INFO Informational messages 6 DEBUG Debugging messages used for NDBCLUSTER  development The  STATISTICS  category can provide a great deal of useful data. See Section 23.5.3.3, “Using CLUSTERLOG STATISTICS in the NDB Cluster Management Client” , for more information. Thresholds are used to filter events within each category. For example, a  STARTUP  event with a priority of 3 is not logged unless the threshold for  STARTUP  is set to 3 or higher. Only events with priority 3 or lower are sent if the threshold is 3. The following table shows the event severity levels. These correspond to Unix  syslog  levels, except for  LOG_EMERG  and LOG_NOTICE , which are not used or mapped. Event severity levels can be turned on or off (using  CLUSTERLOG FILTER —see above). If a severity level is turned on, then all events with a priority less than or equal to the category thresholds are logged. If the severity level is turned off then no events belonging to that severity level are logged. Cluster log levels are set on a per  ndb_mgmd , per subscriber basis. This means that, in an NDB Cluster with multiple management servers, using a  CLUSTERLOG command in an instance of  ndb_mgm  connected to one management server affects Important Note Table 23.54 Event severity levels 4465