Add network direction
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
The add_network_direction processor attempts to compute the perimeter-based network direction when given a source and destination IP address and a list of internal networks.
- add_network_direction:
source: source.ip
destination: destination.ip
target: network.direction
internal_networks: [ private ]
Elastic Agent processors execute before ingest pipelines, which means that they process the raw event data rather than the final event sent to Elasticsearch. For related limitations, refer to What are some limitations of using processors?
| Name | Required | Default | Description |
|---|---|---|---|
source |
Yes | Source IP. | |
destination |
Yes | Destination IP. | |
target |
Yes | Target field where the network direction will be written. | |
internal_networks |
Yes | List of internal networks. The value can contain either CIDR blocks or a list of special values enumerated in the network section of Conditions. |