---
title: Transaction Event fields
description: These fields contain data about the transaction itself. 
url: https://www.elastic.co/elastic/docs-builder/docs/3016/reference/beats/packetbeat/exported-fields-trans_event
products:
  - Beats
  - Packetbeat
applies_to:
  - Elastic Cloud Serverless: Generally available
  - Elastic Stack: Generally available
---

# Transaction Event fields
These fields contain data about the transaction itself.
<definitions>
  <definition term="status">
    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.
    required: True
  </definition>
  <definition term="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).
  </definition>
  <definition term="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.
  </definition>
  <definition term="path">
    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.
    required: True
  </definition>
  <definition term="query">
    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 like `SELECT id from users where name=test`.
    type: keyword
  </definition>
  <definition term="params">
    The request parameters. For HTTP, these are the POST or GET parameters. For Thrift-RPC, these are the parameters from the request.
    type: text
  </definition>
  <definition term="notes">
    Messages from Packetbeat itself. This field usually contains error messages for interpreting the raw data. This information can be helpful for troubleshooting.
    type: alias
    alias to: error.message
  </definition>
</definitions>