Movatterモバイル変換

Some elements appear in every<AUDIT_RECORD> element. Others are optional and may appear depending on the audit record type.

Order of elements within an<AUDIT_RECORD> element is not guaranteed.

Element values are not fixed length. Long values may be truncated as indicated in the element descriptions given later.

The<,>,", and& characters are encoded as<,>,", and&, respectively. NUL bytes (U+00) are encoded as the? character.

Characters not valid as XML characters are encoded using numeric character references. Valid XML characters are:

#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]

<NAME>

A string representing the type of instruction that generated the audit event, such as a command that the server received from a client.

Example:

<NAME>Query</NAME>

Some common<NAME> values:

Audit    When auditing starts, which may be server startup timeConnect  When a client connects, also known as logging inQuery    An SQL statement (executed directly)Prepare  Preparation of an SQL statement; usually followed by ExecuteExecute  Execution of an SQL statement; usually follows PrepareShutdown Server shutdownQuit     When a client disconnectsNoAudit  Auditing has been turned off

The possible values areAudit,Binlog Dump,Change user,Close stmt,Connect Out,Connect,Create DB,Daemon,Debug,Delayed insert,Drop DB,Execute,Fetch,Field List,Init DB,Kill,Long Data,NoAudit,Ping,Prepare,Processlist,Query,Quit,Refresh,Register Slave,Reset stmt,Set option,Shutdown,Sleep,Statistics,Table Dump,TableDelete,TableInsert,TableRead,TableUpdate,Time.

Many of these values correspond to theCOM_xxx command values listed in themy_command.h header file. For example,Create DB andChange user correspond toCOM_CREATE_DB andCOM_CHANGE_USER, respectively.

Events having<NAME> values ofTableXXX accompanyQuery events. For example, the following statement generates oneQuery event, twoTableRead events, and aTableInsert events:

INSERT INTO t3 SELECT t1.* FROM t1 JOIN t2;

EachTableXXX event contains<TABLE> and<DB> elements to identify the table to which the event refers and the database that contains the table.

<RECORD_ID>

A unique identifier for the audit record. The value is composed from a sequence number and timestamp, in the formatSEQ_TIMESTAMP. When the audit log plugin opens the audit log file, it initializes the sequence number to the size of the audit log file, then increments the sequence by 1 for each record logged. The timestamp is a UTC value inYYYY-MM-DDThh:mm:ss format indicating the date and time when the audit log plugin opened the file.

Example:

<RECORD_ID>12_2019-10-03T14:06:33</RECORD_ID>

<TIMESTAMP>

A string representing a UTC value inYYYY-MM-DDThh:mm:ss UTC format indicating the date and time when the audit event was generated. For example, the event corresponding to execution of an SQL statement received from a client has a<TIMESTAMP> value occurring after the statement finishes, not when it was received.

Example:

<TIMESTAMP>2019-10-03T14:09:45 UTC</TIMESTAMP>

<COMMAND_CLASS>

A string that indicates the type of action performed.

Example:

<COMMAND_CLASS>drop_table</COMMAND_CLASS>

The values correspond to thestatement/sql/xxx command counters. For example,xxx isdrop_table andselect forDROP TABLE andSELECT statements, respectively. The following statement displays the possible names:

SELECT REPLACE(EVENT_NAME, 'statement/sql/', '') AS nameFROM performance_schema.events_statements_summary_global_by_event_nameWHERE EVENT_NAME LIKE 'statement/sql/%'ORDER BY name;

<CONNECTION_ATTRIBUTES>

Events with a<COMMAND_CLASS> value ofconnect may include a<CONNECTION_ATTRIBUTES> element to display the connection attributes passed by the client at connect time. (For information about these attributes, which are also exposed in Performance Schema tables, seeSection 29.12.9, “Performance Schema Connection Attribute Tables”.)

The<CONNECTION_ATTRIBUTES> element contains one<ATTRIBUTE> element per attribute, each of which contains<NAME> and<VALUE> elements to indicate the attribute name and value, respectively.

Example:

<CONNECTION_ATTRIBUTES> <ATTRIBUTE>  <NAME>_pid</NAME>  <VALUE>42794</VALUE> </ATTRIBUTE> <ATTRIBUTE>  <NAME>_os</NAME>  <VALUE>macos0.14</VALUE> </ATTRIBUTE> <ATTRIBUTE>  <NAME>_platform</NAME>  <VALUE>x86_64</VALUE> </ATTRIBUTE> <ATTRIBUTE>  <NAME>_client_version</NAME>  <VALUE>8.4.0</VALUE> </ATTRIBUTE> <ATTRIBUTE>  <NAME>_client_name</NAME>  <VALUE>libmysql</VALUE> </ATTRIBUTE> <ATTRIBUTE>  <NAME>program_name</NAME>  <VALUE>mysqladmin</VALUE> </ATTRIBUTE></CONNECTION_ATTRIBUTES>

If no connection attributes are present in the event, none are logged and no<CONNECTION_ATTRIBUTES> element appears. This can occur if the connection attempt is unsuccessful, the client passes no attributes, or the connection occurs internally such as during server startup or when initiated by a plugin.

<CONNECTION_ID>

An unsigned integer representing the client connection identifier. This is the same as the value returned by theCONNECTION_ID() function within the session.

Example:

<CONNECTION_ID>127</CONNECTION_ID>

<CONNECTION_TYPE>

The security state of the connection to the server. Permitted values areTCP/IP (TCP/IP connection established without encryption),SSL/TLS (TCP/IP connection established with encryption),Socket (Unix socket file connection),Named Pipe (Windows named pipe connection), andShared Memory (Windows shared memory connection).

Example:

<CONNECTION_TYPE>SSL/TLS</CONNECTION_TYPE>

<DB>

A string representing a database name.

Example:

<DB>test</DB>

For connect events, this element indicates the default database; the element is empty if there is no default database. For table-access events, the element indicates the database to which the accessed table belongs.

<HOST>

A string representing the client host name.

Example:

<HOST>localhost</HOST>

<IP>

A string representing the client IP address.

Example:

<IP>127.0.0.1</IP>

<MYSQL_VERSION>

A string representing the MySQL server version. This is the same as the value of theVERSION() function orversion system variable.

Example:

<MYSQL_VERSION>5.7.21-log</MYSQL_VERSION>

<OS_LOGIN>

A string representing the external user name used during the authentication process, as set by the plugin used to authenticate the client. With native (built-in) MySQL authentication, or if the plugin does not set the value, this element is empty. The value is the same as that of theexternal_user system variable (seeSection 8.2.19, “Proxy Users”).

Example:

<OS_LOGIN>jeffrey</OS_LOGIN>

<OS_VERSION>

A string representing the operating system on which the server was built or is running.

Example:

<OS_VERSION>x86_64-Linux</OS_VERSION>

<PRIV_USER>

A string representing the user that the server authenticated the client as. This is the user name that the server uses for privilege checking, and may differ from the<USER> value.

Example:

<PRIV_USER>jeffrey</PRIV_USER>

<PROXY_USER>

A string representing the proxy user (seeSection 8.2.19, “Proxy Users”). The value is empty if user proxying is not in effect.

Example:

<PROXY_USER>developer</PROXY_USER>

<SERVER_ID>

An unsigned integer representing the server ID. This is the same as the value of theserver_id system variable.

Example:

<SERVER_ID>1</SERVER_ID>

<SQLTEXT>

A string representing the text of an SQL statement. The value can be empty. Long values may be truncated. The string, like the audit log file itself, is written using UTF-8 (up to 4 bytes per character), so the value may be the result of conversion. For example, the original statement might have been received from the client as an SJIS string.

Example:

<SQLTEXT>DELETE FROM t1</SQLTEXT>

<STARTUP_OPTIONS>

A string representing the options that were given on the command line or in option files when the MySQL server was started. The first option is the path to the server executable.

Example:

<STARTUP_OPTIONS>/usr/local/mysql/bin/mysqld  --port=3306 --log_output=FILE</STARTUP_OPTIONS>

<STATUS>

An unsigned integer representing the command status: 0 for success, nonzero if an error occurred. This is the same as the value of themysql_errno() C API function. See the description for<STATUS_CODE> for information about how it differs from<STATUS>.

The audit log does not contain the SQLSTATE value or error message. To see the associations between error codes, SQLSTATE values, and messages, seeServer Error Message Reference.

Warnings are not logged.

Example:

<STATUS>1051</STATUS>

<STATUS_CODE>

An unsigned integer representing the command status: 0 for success, 1 if an error occurred.

TheSTATUS_CODE value differs from theSTATUS value:STATUS_CODE is 0 for success and 1 for error, which is compatible with the EZ_collector consumer for Audit Vault.STATUS is the value of themysql_errno() C API function. This is 0 for success and nonzero for error, and thus is not necessarily 1 for error.

Example:

<STATUS_CODE>0</STATUS_CODE>

<TABLE>

A string representing a table name.

Example:

<TABLE>t3</TABLE>

<USER>

A string representing the user name sent by the client. This may differ from the<PRIV_USER> value.

Example:

<USER>root[root] @ localhost [127.0.0.1]</USER>

<VERSION>

An unsigned integer representing the version of the audit log file format.

Example:

<VERSION>1</VERSION>

Some attributes appear in every<AUDIT_RECORD> element. Others are optional and may appear depending on the audit record type.

Order of attributes within an<AUDIT_RECORD> element is not guaranteed.

Attribute values are not fixed length. Long values may be truncated as indicated in the attribute descriptions given later.

The<,>,", and& characters are encoded as<,>,", and&, respectively. NUL bytes (U+00) are encoded as the? character.

Characters not valid as XML characters are encoded using numeric character references. Valid XML characters are:

#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]

NAME

A string representing the type of instruction that generated the audit event, such as a command that the server received from a client.

Example:NAME="Query"

Some commonNAME values:

Audit    When auditing starts, which may be server startup timeConnect  When a client connects, also known as logging inQuery    An SQL statement (executed directly)Prepare  Preparation of an SQL statement; usually followed by ExecuteExecute  Execution of an SQL statement; usually follows PrepareShutdown Server shutdownQuit     When a client disconnectsNoAudit  Auditing has been turned off

The possible values areAudit,Binlog Dump,Change user,Close stmt,Connect Out,Connect,Create DB,Daemon,Debug,Delayed insert,Drop DB,Execute,Fetch,Field List,Init DB,Kill,Long Data,NoAudit,Ping,Prepare,Processlist,Query,Quit,Refresh,Register Slave,Reset stmt,Set option,Shutdown,Sleep,Statistics,Table Dump,TableDelete,TableInsert,TableRead,TableUpdate,Time.

Many of these values correspond to theCOM_xxx command values listed in themy_command.h header file. For example,"Create DB" and"Change user" correspond toCOM_CREATE_DB andCOM_CHANGE_USER, respectively.

Events havingNAME values ofTableXXX accompanyQuery events. For example, the following statement generates oneQuery event, twoTableRead events, and aTableInsert events:

INSERT INTO t3 SELECT t1.* FROM t1 JOIN t2;

EachTableXXX event hasTABLE andDB attributes to identify the table to which the event refers and the database that contains the table.

Connect events for old-style XML audit log format do not include connection attributes.

RECORD_ID

A unique identifier for the audit record. The value is composed from a sequence number and timestamp, in the formatSEQ_TIMESTAMP. When the audit log plugin opens the audit log file, it initializes the sequence number to the size of the audit log file, then increments the sequence by 1 for each record logged. The timestamp is a UTC value inYYYY-MM-DDThh:mm:ss format indicating the date and time when the audit log plugin opened the file.

Example:RECORD_ID="12_2019-10-03T14:25:00"

TIMESTAMP

A string representing a UTC value inYYYY-MM-DDThh:mm:ss UTC format indicating the date and time when the audit event was generated. For example, the event corresponding to execution of an SQL statement received from a client has aTIMESTAMP value occurring after the statement finishes, not when it was received.

Example:TIMESTAMP="2019-10-03T14:25:32 UTC"

COMMAND_CLASS

A string that indicates the type of action performed.

Example:COMMAND_CLASS="drop_table"

The values correspond to thestatement/sql/xxx command counters. For example,xxx isdrop_table andselect forDROP TABLE andSELECT statements, respectively. The following statement displays the possible names:

SELECT REPLACE(EVENT_NAME, 'statement/sql/', '') AS nameFROM performance_schema.events_statements_summary_global_by_event_nameWHERE EVENT_NAME LIKE 'statement/sql/%'ORDER BY name;

CONNECTION_ID

An unsigned integer representing the client connection identifier. This is the same as the value returned by theCONNECTION_ID() function within the session.

Example:CONNECTION_ID="127"

CONNECTION_TYPE

The security state of the connection to the server. Permitted values areTCP/IP (TCP/IP connection established without encryption),SSL/TLS (TCP/IP connection established with encryption),Socket (Unix socket file connection),Named Pipe (Windows named pipe connection), andShared Memory (Windows shared memory connection).

Example:CONNECTION_TYPE="SSL/TLS"

DB

A string representing a database name.

Example:DB="test"

For connect events, this attribute indicates the default database; the attribute is empty if there is no default database. For table-access events, the attribute indicates the database to which the accessed table belongs.

HOST

A string representing the client host name.

Example:HOST="localhost"

IP

A string representing the client IP address.

Example:IP="127.0.0.1"

MYSQL_VERSION

A string representing the MySQL server version. This is the same as the value of theVERSION() function orversion system variable.

Example:MYSQL_VERSION="5.7.21-log"

OS_LOGIN

A string representing the external user name used during the authentication process, as set by the plugin used to authenticate the client. With native (built-in) MySQL authentication, or if the plugin does not set the value, this attribute is empty. The value is the same as that of theexternal_user system variable (seeSection 8.2.19, “Proxy Users”).

Example:OS_LOGIN="jeffrey"

OS_VERSION

A string representing the operating system on which the server was built or is running.

Example:OS_VERSION="x86_64-Linux"

PRIV_USER

A string representing the user that the server authenticated the client as. This is the user name that the server uses for privilege checking, and it may differ from theUSER value.

Example:PRIV_USER="jeffrey"

PROXY_USER

A string representing the proxy user (seeSection 8.2.19, “Proxy Users”). The value is empty if user proxying is not in effect.

Example:PROXY_USER="developer"

SERVER_ID

An unsigned integer representing the server ID. This is the same as the value of theserver_id system variable.

Example:SERVER_ID="1"

SQLTEXT

A string representing the text of an SQL statement. The value can be empty. Long values may be truncated. The string, like the audit log file itself, is written using UTF-8 (up to 4 bytes per character), so the value may be the result of conversion. For example, the original statement might have been received from the client as an SJIS string.

Example:SQLTEXT="DELETE FROM t1"

STARTUP_OPTIONS

A string representing the options that were given on the command line or in option files when the MySQL server was started.

Example:STARTUP_OPTIONS="--port=3306 --log_output=FILE"

STATUS

An unsigned integer representing the command status: 0 for success, nonzero if an error occurred. This is the same as the value of themysql_errno() C API function. See the description forSTATUS_CODE for information about how it differs fromSTATUS.

The audit log does not contain the SQLSTATE value or error message. To see the associations between error codes, SQLSTATE values, and messages, seeServer Error Message Reference.

Warnings are not logged.

Example:STATUS="1051"

STATUS_CODE

An unsigned integer representing the command status: 0 for success, 1 if an error occurred.

TheSTATUS_CODE value differs from theSTATUS value:STATUS_CODE is 0 for success and 1 for error, which is compatible with the EZ_collector consumer for Audit Vault.STATUS is the value of themysql_errno() C API function. This is 0 for success and nonzero for error, and thus is not necessarily 1 for error.

Example:STATUS_CODE="0"

TABLE

A string representing a table name.

Example:TABLE="t3"

USER

A string representing the user name sent by the client. This may differ from thePRIV_USER value.

VERSION

An unsigned integer representing the version of the audit log file format.

Example:VERSION="1"

Some items appear in every audit record. Others are optional and may appear depending on the audit record type.

Order of items within an audit record is not guaranteed.

Item values are not fixed length. Long values may be truncated as indicated in the item descriptions given later.

The" and\ characters are encoded as\" and\\, respectively.

account

The MySQL account associated with the event. The value is a hash containing these items equivalent to the value of theCURRENT_USER() function within the section:user,host.

Example:

"account": { "user": "root", "host": "localhost" }

class

A string representing the event class. The class defines the type of event, when taken together with theevent item that specifies the event subclass.

Example:

"class": "connection"

The following table shows the permitted combinations ofclass andevent values.

connection_data

Information about a client connection. The value is a hash containing these items:connection_type,status,db, and possiblyconnection_attributes. This item occurs only for audit records with aclass value ofconnection.

Example:

"connection_data": { "connection_type": "ssl",                     "status": 0,                     "db": "test" }

Events with aclass value ofconnection andevent value ofconnect may include aconnection_attributes item to display the connection attributes passed by the client at connect time. (For information about these attributes, which are also exposed in Performance Schema tables, seeSection 29.12.9, “Performance Schema Connection Attribute Tables”.)

Theconnection_attributes value is a hash that represents each attribute by its name and value.

Example:

"connection_attributes": {  "_pid": "43236",  "_os": "macos0.14",  "_platform": "x86_64",  "_client_version": "8.4.0",  "_client_name": "libmysql",  "program_name": "mysqladmin"}

If no connection attributes are present in the event, none are logged and noconnection_attributes item appears. This can occur if the connection attempt is unsuccessful, the client passes no attributes, or the connection occurs internally such as during server startup or when initiated by a plugin.

connection_id

An unsigned integer representing the client connection identifier. This is the same as the value returned by theCONNECTION_ID() function within the session.

Example:

"connection_id": 5

event

A string representing the subclass of the event class. The subclass defines the type of event, when taken together with theclass item that specifies the event class. For more information, see theclass item description.

Example:

"event": "connect"

general_data

Information about an executed statement or command. The value is a hash containing these items:command,sql_command,query,status. This item occurs only for audit records with aclass value ofgeneral.

Example:

"general_data": { "command": "Query",                  "sql_command": "show_variables",                  "query": "SHOW VARIABLES",                  "status": 0 }

id

An unsigned integer representing an event ID.

Example:

"id": 2

For audit records that have the sametimestamp value, theirid values distinguish them and form a sequence. Within the audit log,timestamp/id pairs are unique. These pairs are bookmarks that identify event locations within the log.

login

Information indicating how a client connected to the server. The value is a hash containing these items:user,os,ip,proxy.

Example:

"login": { "user": "root", "os": "", "ip": "::1", "proxy": "" }

query_statistics

Optional query statistics for outlier detection. The value is a hash containing these items:query_time,rows_sent,rows_examined,bytes_received,bytes_sent. For instructions to set up the query statistics, seeAdding Query Statistics for Outlier Detection.

Example:

"query_statistics": { "query_time": 0.116250,                      "bytes_sent": 18384,                      "bytes_received": 78858,                      "rows_sent": 3,                      "rows_examined": 20878 }

shutdown_data

Information pertaining to audit log plugin termination. The value is a hash containing these items:server_id This item occurs only for audit records withclass andevent values ofaudit andshutdown, respectively.

Example:

"shutdown_data": { "server_id": 1 }

startup_data

Information pertaining to audit log plugin initialization. The value is a hash containing these items:server_id,os_version,mysql_version,args. This item occurs only for audit records withclass andevent values ofaudit andstartup, respectively.

Example:

"startup_data": { "server_id": 1,                  "os_version": "i686-Linux",                  "mysql_version": "5.7.21-log",                  "args": ["/usr/local/mysql/bin/mysqld",                           "--loose-audit-log-format=JSON",                           "--log-error=log.err",                           "--pid-file=mysqld.pid",                           "--port=3306" ] }

table_access_data

Information about an access to a table. The value is a hash containing these items:db,table,query,sql_command, This item occurs only for audit records with aclass value oftable_access.

Example:

"table_access_data": { "db": "test",                       "table": "t1",                       "query": "INSERT INTO t1 (i) VALUES(1),(2),(3)",                       "sql_command": "insert" }

time

This field is similar to that in thetimestamp field, but the value is an integer and represents the UNIX timestamp value indicating the date and time when the audit event was generated.

Example:

"time" : 1618498687

Thetime field occurs in JSON-format log files only if theaudit_log_format_unix_timestamp system variable is enabled.

timestamp

A string representing a UTC value inYYYY-MM-DD hh:mm:ss format indicating the date and time when the audit event was generated. For example, the event corresponding to execution of an SQL statement received from a client has atimestamp value occurring after the statement finishes, not when it was received.

Example:

"timestamp": "2019-10-03 13:50:01"

For audit records that have the sametimestamp value, theirid values distinguish them and form a sequence. Within the audit log,timestamp/id pairs are unique. These pairs are bookmarks that identify event locations within the log.

args

An array of options that were given on the command line or in option files when the MySQL server was started. The first option is the path to the server executable.

Example:

"args": ["/usr/local/mysql/bin/mysqld",         "--loose-audit-log-format=JSON",         "--log-error=log.err",         "--pid-file=mysqld.pid",         "--port=3306" ]

bytes_received

The number of bytes received from the client. This item is part of the optional query statistics. For this field to be populated, the system variablelog_slow_extra must be set toON.

Example:

"bytes_received": 78858

bytes_sent

The number of bytes sent to the client. This item is part of the optional query statistics. For this field to be populated, the system variablelog_slow_extra must be set toON.

Example:

"bytes_sent": 18384

command

A string representing the type of instruction that generated the audit event, such as a command that the server received from a client.

Example:

"command": "Query"

connection_type

The security state of the connection to the server. Permitted values aretcp/ip (TCP/IP connection established without encryption),ssl (TCP/IP connection established with encryption),socket (Unix socket file connection),named_pipe (Windows named pipe connection), andshared_memory (Windows shared memory connection).

Example:

"connection_type": "tcp/tcp"

db

A string representing a database name. Forconnection_data, it is the default database. Fortable_access_data, it is the table database.

Example:

"db": "test"

host

A string representing the client host name.

Example:

"host": "localhost"

ip

A string representing the client IP address.

Example:

"ip": "::1"

mysql_version

A string representing the MySQL server version. This is the same as the value of theVERSION() function orversion system variable.

Example:

"mysql_version": "5.7.21-log"

os

A string representing the external user name used during the authentication process, as set by the plugin used to authenticate the client. With native (built-in) MySQL authentication, or if the plugin does not set the value, this attribute is empty. The value is the same as that of theexternal_user system variable. SeeSection 8.2.19, “Proxy Users”.

Example:

"os": "jeffrey"

os_version

A string representing the operating system on which the server was built or is running.

Example:

"os_version": "i686-Linux"

proxy

A string representing the proxy user (seeSection 8.2.19, “Proxy Users”). The value is empty if user proxying is not in effect.

Example:

"proxy": "developer"

query

A string representing the text of an SQL statement. The value can be empty. Long values may be truncated. The string, like the audit log file itself, is written using UTF-8 (up to 4 bytes per character), so the value may be the result of conversion. For example, the original statement might have been received from the client as an SJIS string.

Example:

"query": "DELETE FROM t1"

query_time

The query execution time in microseconds (if thelonglong data type is selected) or seconds (if thedouble data type is selected). This item is part of the optional query statistics.

Example:

"query_time": 0.116250

rows_examined

The number of rows accessed during the query. This item is part of the optional query statistics.

Example:

"rows_examined": 20878

rows_sent

The number of rows sent to the client as a result. This item is part of the optional query statistics.

Example:

"rows_sent": 3

server_id

An unsigned integer representing the server ID. This is the same as the value of theserver_id system variable.

Example:

"server_id": 1

sql_command

A string that indicates the SQL statement type.

Example:

"sql_command": "insert"

The values correspond to thestatement/sql/xxx command counters. For example,xxx isdrop_table andselect forDROP TABLE andSELECT statements, respectively. The following statement displays the possible names:

SELECT REPLACE(EVENT_NAME, 'statement/sql/', '') AS nameFROM performance_schema.events_statements_summary_global_by_event_nameWHERE EVENT_NAME LIKE 'statement/sql/%'ORDER BY name;

status

An unsigned integer representing the command status: 0 for success, nonzero if an error occurred. This is the same as the value of themysql_errno() C API function.

The audit log does not contain the SQLSTATE value or error message. To see the associations between error codes, SQLSTATE values, and messages, seeServer Error Message Reference.

Warnings are not logged.

Example:

"status": 1051

table

A string representing a table name.

Example:

"table": "t1"

user

A string representing a user name. The meaning differs depending on the item within whichuser occurs:

Example:

"user": "root"