content_image/870957.jpg content_image/870969.jpg content_image/870958.jpg content_image/870970.jpg
<img src='content_image/870957.jpg'>

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. 

<img src='content_image/870969.jpg'>

## Note 

These correspond to Unix syslog  levels, except for LOG_EMERG  and LOG_NOTICE , which are not used or mapped. 

<img src='content_image/870958.jpg'>

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. 

<img src='content_image/870970.jpg'>

## Important 

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 

