Pensando 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
pensando Module
Fields from Pensando logs.
The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in beta and is not ready for production usage. For beta features, the design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features. Specific Support terms apply. 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.
Stack
Beta
Beta
Fields for Pensando DFW
pensando.dfw.action-
Action on the flow.
type: keyword
pensando.dfw.app_id-
Application ID
type: integer
pensando.dfw.destination_address-
Address of destination.
type: keyword
pensando.dfw.destination_port-
Port of destination.
type: integer
pensando.dfw.direction-
Direction of the flow
type: keyword
pensando.dfw.protocol-
Protocol of the flow
type: keyword
pensando.dfw.rule_id-
Rule ID that was matched.
type: keyword
pensando.dfw.session_id-
Session ID of the flow
type: integer
pensando.dfw.session_state-
Session state of the flow.
type: keyword
pensando.dfw.source_address-
Source address of the flow.
type: keyword
pensando.dfw.source_port-
Source port of the flow.
type: integer
pensando.dfw.timestamp-
Timestamp of the log.
type: date