(mysql.info) mysql-cluster-logging-management-commands

(mysql.info) mysql-cluster-event-reports
(mysql.info) mysql-cluster-log-events
 
 15.6.3.1 Logging Management Commands
 ....................................
 
 The following management commands are related to the cluster log:
 
    * `CLUSTERLOG ON'
 
      Turns the cluster log on.
 
    * `CLUSTERLOG OFF'
 
      Turns the cluster log off.
 
    * `CLUSTERLOG INFO'
 
      Provides information about cluster log settings.
 
    * `NODE_ID CLUSTERLOG CATEGORY=THRESHOLD'
 
      Logs CATEGORY events with priority less than or equal to THRESHOLD
      in the cluster log.
 
    * `CLUSTERLOG FILTER SEVERITY_LEVEL'
 
      Toggles cluster logging of events of the specified SEVERITY_LEVEL.
 
 The following table describes the default setting (for all data nodes)
 of the cluster log category threshold. If an event has a priority with
 a value lower than or equal to the priority threshold, it is reported
 in the cluster log.
 
 Note that events are reported per data node, and that the threshold can
 be set to different values on different nodes.
 
 *Category*             *Default threshold (All data nodes)*
 `STARTUP'              *7*
 `SHUTDOWN'             *7*
 `STATISTICS'           *7*
 `CHECKPOINT'           *7*
 `NODERESTART'          *7*
 `CONNECTION'           *7*
 `ERROR'                *15*
 `INFO'                 *7*
 
 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 changed to 3 or lower. 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.)
 
 *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 `NDB Cluster'
                        development
 
 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.
Info Catalog
(mysql.info) mysql-cluster-event-reports
(mysql.info) mysql-cluster-log-events
automatically generated byinfo2html