Error logs event¶

https://dev.mysql.com/doc/refman/8.0/en/error-log-event-fields.html

Core Error Event Fields

These error event fields are core fields:

time

The event timestamp, with microsecond precision.

msg

The event message string.

prio

The event priority, to indicate a system, error, warning, or note/information event. This field corresponds to severity in syslog. The following table shows the possible priority levels.

Event Type Numeric Priority System event 0 Error event 1 Warning event 2 Note/information event 3 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 label:

OS_errno

The operating system error number.

OS_errmsg

The operating system error message.

label

The label corresponding to the prio value, as a string.

Identification of the client for which the event occurred:

user

The client user.

host

The client host.

thread

The ID of the thread within mysqld responsible for producing the error event. This ID indicates which part of the server produced the event, and is consistent with general query log and slow query log messages, which include the connection thread ID.

query_id

The query ID.

Debugging information:

source_file

The source file in which the event occurred, without any leading path.

source_line

The line within the source file at which the event occurred.

function

The function in which the event occurred.

component

The component or plugin in which the event occurred.

Reference¶

https://www.contrive.mobi/aviorapi/HTTPMETHODS.html