Configure Your Applications to Send Trace Data to Cisco AppDynamics Distribution of OpenTelemetry Collector

This page describes how to configure your applications to send trace data to the Cisco AppDynamics Distribution of OpenTelemetry Collector.

Before You Begin

The configuration described on this page assumes that:

Your applications are running in a supported Kubernetes® cluster. See Software Requirements.
You have installed Kubernetes and App Service Monitoring using Helm charts. See Install Kubernetes and App Service Monitoring.
Your applications are instrumented with OpenTelemetry™, using an agent or SDK.
You have not deployed an OpenTelemetry Collector and will send trace data directly from your applications to the Cisco AppDynamics Distribution of OpenTelemetry Collector.

Error rendering macro 'excerpt-include'

User 'null' does not have permission to view the page.

Prerequisites

Ensure the service.name resource attribute is configured in the instrumented applications using OTEL_SERVICE_NAME or OTEL_RESOURCE_ATTRIBUTES. See https://opentelemetry.io/docs/concepts/sdk-configuration/general-sdk-configuration/.

Configure the Exporter Endpoint for Your Applications

The following table lists the endpoint values you configure for the OTLP exporter used by your applications, depending on whether you want to use a secure connection and the target protocol (HTTP or gRPC). The endpoints use the Collector service from the appdynamics namespace, deployed by the Kubernetes and App Service Monitoring Helm charts.

	Insecure	Secure
gRPC Endpoint	`http://appdynamics-otel-collector-service.appdynamics.svc.cluster.local:4317`	`https://appdynamics-otel-collector-service.appdynamics.svc.cluster.local:4317`
HTTP Endpoint	`http://appdynamics-otel-collector-service.appdynamics.svc.cluster.local:4318`	`https://appdynamics-otel-collector-service.appdynamics.svc.cluster.local:4318`

Use the OTEL_EXPORTER_OTLP_ENDPOINT environment variable to configure the endpoint. See https://opentelemetry.io/docs/concepts/sdk-configuration/otlp-exporter-configuration/.

In the following Kubernetes deployment manifest snippet, OTEL_EXPORTER_OTLP_ENDPOINT is configured to use an insecure connection and the gRPC protocol:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: ad-service
spec:
  template:
    ...
    spec:
      containers:
        - name: ad-service
          image: otel/demo:v0.2.0-alpha-adservice
          env:
          - name: OTEL_EXPORTER_OTLP_ENDPOINT
            value: http://appdynamics-otel-collector-service.appdynamics.svc.cluster.local:4317
          ...

YML

For a secure connection, set the endpoint as shown:

- name: OTEL_EXPORTER_OTLP_PROTOCOL
  value: grpc          
- name: OTEL_EXPORTER_OTLP_ENDPOINT
  value: https://appdynamics-otel-collector-service.appdynamics.svc.cluster.local:4317

CODE

- name: OTEL_EXPORTER_OTLP_PROTOCOL
  value: http/protobuf          
- name: OTEL_EXPORTER_OTLP_ENDPOINT 
  value: https://appdynamics-otel-collector-service.appdynamics.svc.cluster.local:4318

CODE

For an insecure connection, set the endpoint as shown:

- name: OTEL_EXPORTER_OTLP_PROTOCOL
  value: grpc          
- name: OTEL_EXPORTER_OTLP_ENDPOINT
  value: http://appdynamics-otel-collector-service.appdynamics.svc.cluster.local:4317

CODE

- name: OTEL_EXPORTER_OTLP_PROTOCOL
  value: http/protobuf          
- name: OTEL_EXPORTER_OTLP_ENDPOINT 
  value: http://appdynamics-otel-collector-service.appdynamics.svc.cluster.local:4318

CODE

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.