Common fields
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
These fields contain data about the environment in which the transaction or flow was captured.
type-
The type of the transaction (for example, HTTP, MySQL, Redis, or RUM) or "flow" in case of flows.
required: True
server.process.name- The name of the process that served the transaction.
server.process.args- The command-line of the process that served the transaction.
server.process.executable- Absolute path to the server process executable.
server.process.working_directory- The working directory of the server process.
server.process.start- The time the server process started.
client.process.name- The name of the process that initiated the transaction.
client.process.args- The command-line of the process that initiated the transaction.
client.process.executable- Absolute path to the client process executable.
client.process.working_directory- The working directory of the client process.
client.process.start- The time the client process started.
real_ip-
If the server initiating the transaction is a proxy, this field contains the original client IP address. For HTTP, for example, the IP address extracted from a configurable HTTP header, by default
X-Forwarded-For. Unless this field is disabled, it always has a value, and it matches theclient_ipfor non proxy clients.type: alias
alias to: network.forwarded_ip
transport-
The transport protocol used for the transaction. If not specified, then tcp is assumed.
type: alias
alias to: network.transport