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

The prio  value is numeric. Related to it, an error event may also include an optional label  field representing the priority as a string. For example, an event with a prio  value of 2 may have a label value of ’Warning’ . 

Filter components may include or drop error events based on priority, except that system events are mandatory and cannot be dropped. 

In general, message priorities are determined as follows: 

Is the situation or event actionable? 

•Yes: Is the situation or event ignorable? 

•Yes: Priority is warning. 

•No: Priority is error. 

•No: Is the situation or event mandatory? 

•Yes: Priority is system. 

•No: Priority is note/information. 

• err_code 

The event error code, as a number (for example, 1022 ). 

• err_symbol 

The event error symbol, as a string (for example, ’ER_DUP_KEY’ ). 

• SQL_state 

The event SQLSTATE value, as a string (for example, ’23000’ ). 

• subsystem 

The subsystem in which the event occurred. Possible values are InnoDB  (the InnoDB  storage engine), Repl  (the replication subsystem), Server  (otherwise). 

## Optional Error Event Fields 

Optional error event fields fall into the following categories: 

•Additional information about the error, such as the error signaled by the operating system or the error lable: 

• OS_errno 

The operating system error number. 

• OS_errmsg 

