Docs » Supported integrations in Splunk Observability Cloud » Configure application receivers for networks » AWS AppMesh Envoy Proxy

AWS AppMesh Envoy Proxy 🔗

The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the AppMesh monitor type 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.

This integration is available on Kubernetes, Linux, and Windows.

Benefits 🔗

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

Installation 🔗

Follow these steps to deploy this integration:

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

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

  3. Restart the Splunk Distribution of the OpenTelemetry Collector.

Configuration 🔗

To use this integration of a Smart Agent monitor with the Collector:

  1. Include the Smart Agent receiver in your configuration file.

  2. Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

Example 🔗

To activate this integration, add the following to your Collector configuration:

receivers:
  smartagent/appmesh:
    type: appmesh
      ... # Additional config

Next, add the monitor to the service.pipelines.metrics.receivers section of your configuration file:

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

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:

Notes 🔗

  • To learn more about the available in Observability Cloud see Metric types

  • In host-based subscription plans, default metrics are those metrics included in host-based subscriptions in Observability Cloud, such as host, container, or bundled metrics. Custom metrics are not provided by default and might be subject to charges. See Metric categories for more information.

  • In MTS-based subscription plans, all metrics are custom.

  • To add additional metrics, see how to configure extraMetrics in Add additional metrics

Troubleshooting 🔗

If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.

Available to Splunk Observability Cloud customers

Available to prospective customers and free trial users

  • Ask a question and get answers through community support at Splunk Answers .

  • Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.

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