Peer forwarder

Peer forwarder groups events based on the identification keys provided by the supported processors. For service_map_stateful and otel_trace_raw, the identification key is traceId by default and cannot be configured. The aggregate processor is configured using the identification_keys configuration option. From here, you can specify which keys to use for peer forwarder. See Aggregate Processor page for more information about identification keys.

Peer discovery allows Data Prepper to find other nodes that it will communicate with. Currently, peer discovery is provided by a static list, a DNS record lookup, or AWS Cloud Map.

The following sections provide information about discovery modes.

Static discovery mode allows a Data Prepper node to discover nodes using a list of IP addresses or domain names. See the following YAML file for an example of static discovery mode:

DNS lookup

DNS discovery is preferred over static discovery when scaling out a Data Prepper cluster. DNS discovery configures a DNS provider to return a list of Data Prepper hosts when given a single domain name. This list consists of a DNS A record, and a list of IP addresses of a given domain. See the following YAML file for an example of DNS lookup:

  1. peer_forwarder:
  2.   discovery_mode: dns
  3.   domain_name: "data-prepper-cluster.my-domain.net"

AWS Cloud Map provides API-based service discovery as well as DNS-based service discovery.

Your Data Prepper configuration needs to include the following:

  • aws_cloud_map_namespace_name – Set to your AWS Cloud Map namespace name.
  • aws_cloud_map_service_name – Set to the service name within your specified namespace.
  • aws_region – Set to the AWS Region in which your namespace exists.
  • discovery_mode – Set to aws_cloud_map.

Your Data Prepper configuration can optionally include the following:

  • aws_cloud_map_query_parameters – Key-value pairs are used to filter the results based on the custom attributes attached to an instance. Results include only those instances that match all of the specified key-value pairs.

Example configuration

See the following YAML file example of AWS Cloud Map configuration:

IAM policy with necessary permissions

Data Prepper must also be running with the necessary permissions. The following AWS Identity and Access Management (IAM) policy shows the necessary permissions:

  1. {
  2.     "Version": "2012-10-17",
  3.     "Statement": [
  4.             "Sid": "CloudMapPeerForwarder",
  5.             "Effect": "Allow",
  6.             "Action": "servicediscovery:DiscoverInstances",
  7.             "Resource": "*"
  8.         }
  9.     ]
  10. }

The following table provides optional configuration values.

The following table provides optional SSL configuration values that allow you to set up a trust manager for the peer forwarder client in order to connect to other Data Prepper instances.

Example configuration

Authentication is optional and is a Map that enables mutual TLS (mTLS). It can either be mutual_tls or unauthenticated. The default value is unauthenticated. The following YAML file provides an example of authentication:

  1. peer_forwarder:
  2.   authentication:
  3.     mutual_tls:

Core peer forwarder introduces the following custom metrics. All the metrics are prefixed by core.peerForwarder.

Peer forwarder’s timer capability provides the following information:

  • requestForwardingLatency: Measures latency of requests forwarded by the peer forwarder client.
  • requestProcessingLatency: Measures latency of requests processed by the peer forwarder server.

Counter

The following table provides counter metric options.

Measures the number of dynamically discovered peer Data Prepper endpoints. For static mode, the size is fixed.