(mysql.info) mysql-cluster-event-reports

Info Catalog

(mysql.info) mgm-client-commands

(mysql.info) mysql-cluster-management

(mysql.info) mysql-cluster-single-user-mode

 
 15.6.3 Event Reports Generated in MySQL Cluster
 -----------------------------------------------
 

Menu

 
* mysql-cluster-logging-management-commands  Logging Management Commands
* mysql-cluster-log-events     Log Events
 
 In this section, we discuss the types of event logs provided by MySQL
 Cluster, and the types of events that are logged.
 
 MySQL Cluster provides two types of event log. These are the *cluster
 log*, which includes events generated by all cluster nodes, and *node
 logs*, which are local to each data node.
 
 Output generated by cluster event logging can have multiple
 destinations including a file, the management server console window, or
 `syslog'. Output generated by node event logging is written to the data
 node's console window.
 
 Both types of event logs can be set to log different subsets of events.
 
 * The cluster log is the log recommended for most uses because it
 provides logging information for an entire cluster in a single file.
 Node logs are intended to be used only during application development,
 or for debugging application code.
 
 Each reportable event can be distinguished according to three different
 criteria:
 
    * _Category_: This can be any one of the following values: `STARTUP',
      `SHUTDOWN', `STATISTICS', `CHECKPOINT', `NODERESTART',
      `CONNECTION', `ERROR', or `INFO'.
 
    * _Priority_: This is represented by one of the numbers from 1 to 15
      inclusive, where 1 indicates `most important' and 15 `least
      important.'
 
    * _Severity Level_: This can be any one of the following values:
      `ALERT', `CRITICAL', `ERROR', `WARNING', `INFO', or `DEBUG'.
 
 Both the cluster log and the node log can be filtered on these
 properties.
 

Info Catalog

(mysql.info) mgm-client-commands

(mysql.info) mysql-cluster-management

(mysql.info) mysql-cluster-single-user-mode