AWS AppMesh Envoy Proxy 🔗
This monitor starts a StatsD monitor to listen to StatsD metrics emitted by AWS AppMesh Envoy Proxy.
To report AppMesh Envoy metrics, enable Envoy StatsD sink on AppMesh and deploy the agent as a sidecar in the services that need to be monitored.
The following example shows an Envoy StatsD configuration:
stats_sinks: - name: "envoy.statsd" config: address: socket_address: address: "127.0.0.1" port_value: 8125 protocol: "UDP" prefix: statsd.appmesh
Since the prefix in metric names needs to be removed before metric name conversion, populate the
with the value of the
metricPrefix configuration for the monitor to remove this specified prefix. If not specified,
prefix field defautls to
To learn more, see the Envoy API reference.
To install this integration:
Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform.
Configure the monitor, as described in the next section.
The Splunk Distribution of OpenTelemetry Collector allows embedding a Smart Agent monitor configuration in an associated Smart Agent Receiver instance.
Note: Providing an AppMesh Envoy monitor entry in your Smart Agent or Collector configuration is required for its use. Use the appropriate form for your agent type.
Smart Agent 🔗
To activate this monitor in the Smart Agent, add the following to your agent configuration:
monitors: # All monitor config goes under this key - type: appmesh ... # Additional config
See Smart Agent example configuration for an autogenerated example of a YAML configuration file, with default values where applicable.
Splunk Distribution of OpenTelemetry Collector 🔗
To activate this monitor in the OpenTelemetry Collector, add the following to your agent configuration:
receivers: smartagent/appmesh: type: appmesh ... # Additional config
To complete the monitor activation, you must also include the
smartagent/appmesh receiver item in a
metrics pipeline. To do this, add the receiver item to the
receivers section of your configuration file.
See configuration examples for specific use cases that show how the collector can integrate and complement existing environments.
Configuration settings 🔗
The following table shows the configuration options for this monitor:
||The host/address on which to bind the UDP listener that accepts statsd datagrams (default:
||The port on which to listen for statsd messages (default:
||A prefix in metric names that needs to be removed before metric name conversion|
Example configurations 🔗
The following is a sample Smart Agent configuration:
monitors: - type: appmesh listenAddress: 0.0.0.0 listenPort: 8125 metricPrefix: statsd.appmesh
These are the metrics available for this integration.