Docs » Available host and application monitors » Configure application receivers for networks » AWS AppMesh Envoy Proxy

AWS AppMesh Envoy Proxy 🔗

Description 🔗

The Splunk Distribution of OpenTelemetry Collector provides this integration as the appmesh monitor for the Smart Agent Receiver.

Use this integration to report metrics from AWS AppMesh Envoy Proxy.

To use this integration, you must also activate the Envoy StatsD sink on AppMesh and deploy the agent as a sidecar in the services that need to be monitored.

Benefits 🔗

After you configure the integration, you can access these features:

  • View metrics. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. For information about dashboards, see View dashboards in Observability Cloud.

  • View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Splunk Infrastructure Monitoring navigators.

  • Access the Metric Finder and search for metrics sent by the monitor. For information, see Use the Metric Finder.

Installation 🔗

Follow these steps to deploy this integration:

  1. Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:

  2. Configure the monitor, as described in the Configuration section.

  3. Restart the Splunk Distribution of OpenTelemetry Collector.

Configuration 🔗

To use this Smart Agent monitor with the Collector, include the smartagent receiver and service pipeline in your configuration file. The Smart Agent receiver is fully supported only on x86_64/amd64 platforms.

See the examples below for more details.

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 integration, include the monitor in a metrics pipeline. Add the monitor item to the service/pipelines/metrics/receivers section of your configuration file. For example:

service:
  pipelines:
    metrics:
      receivers: [smartagent/appmesh]

See the examples directory in the Splunk Distribution of OpenTelemetry Collector GitHub repo at https://githubcom/signalfx/splunk-otel-collector/tree/main/examples for specific use cases that show how the Collector can integrate and complement existing environments.

AWS AppMesh Envoy Proxy 🔗

To configure the AWS AppMesh Envoy Proxy, add the following lines to your configuration of the Envoy StatsD sink on AppMesh:

stats_sinks:
 -
  name: "envoy.statsd"
  config:
   address:
    socket_address:
     address: "127.0.0.1"
     port_value: 8125
     protocol: "UDP"
   prefix: statsd.appmesh

Because you need to remove the prefix in metric names before metric name conversion, set value of the prefix field with the value of the metricPrefix configuration field described in the following table. This change causes the monitor to remove this specified prefix. If you don’t specify a value for the prefix field, it defaults to envoy.

To learn more, see the Envoy API reference.

The following table shows the configuration options for this monitor:

Option

Required

Type

Description

listenAddress

no

string

This host address binds the UDP listener that accepts statsd datagrams. The default value is localhost.

listenPort

no

integer

This value indicates the port on which to listen for statsd messages. The default value is 8125.

metricPrefix

no

string

This string sets the prefix in metric names that the monitor removes before metric name conversion

Metrics 🔗

The following metrics are available for this integration:

Get help 🔗

If you are not able to see your data in Splunk Observability Cloud, try these tips:

To learn about even more support options, see Splunk Customer Success.