Transaction Event fields
editTransaction Event fields
editThese fields contain data about the transaction itself.
-
direction
-
required: True
Indicates whether the transaction is inbound (emitted by server) or outbound (emitted by the client). Values can be in or out. No defaults.
-
status
-
required: True
The high level status of the transaction. The way to compute this value depends on the protocol, but the result has a meaning independent of the protocol.
-
method
-
The command/verb/method of the transaction. For HTTP, this is the method name (GET, POST, PUT, and so on), for SQL this is the verb (SELECT, UPDATE, DELETE, and so on).
-
resource
-
The logical resource that this transaction refers to. For HTTP, this is the URL path up to the last slash (/). For example, if the URL is
/users/1
, the resource is/users
. For databases, the resource is typically the table name. The field is not filled for all transaction types. -
path
-
required: True
The path the transaction refers to. For HTTP, this is the URL. For SQL databases, this is the table name. For key-value stores, this is the key.
-
query
-
type: keyword
The query in a human readable format. For HTTP, it will typically be something like
GET /users/_search?name=test
. For MySQL, it is something likeSELECT id from users where name=test
. -
params
-
type: text
The request parameters. For HTTP, these are the POST or GET parameters. For Thrift-RPC, these are the parameters from the request.
-
notes
-
Messages from Packetbeat itself. This field usually contains error messages for interpreting the raw data. This information can be helpful for troubleshooting.