Configure Your Collector to Send Trace Data to Cisco AppDynamics Distribution of OpenTelemetry Collector Using Spectro Cloud Palette

This page describes how to configure your OpenTelemetry Collector to send trace data to the Cisco AppDynamics Distribution of OpenTelemetry Collector using the Spectro Cloud® Palette user interface.

Before You Begin

The configuration described on this page assumes that:

• Your services are running in a supported Kubernetes® cluster. See Software Requirements.
• Your services are instrumented with OpenTelemetry™ using an agent or SDK.
• You have deployed an OpenTelemetry Collector, which your services are sending trace data to.
• You have installed Kubernetes and App Service Monitoring using the Splunk AppDynamics add-on packs. See Install Kubernetes and App Service Monitoring with Spectro Cloud Palette.
• You have added an add-on pack for your OpenTelemetry Collector in your Cluster Profile.

This document contains references to third-party documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.

Prerequisites

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

Configure Your OpenTelemetry Collector

These are the high-level steps:

1. Navigate to the Cluster Profile
2. Configure Endpoint Values
3. Save the Cluster Profile

1. Navigate to the Cluster Profile

1. Log into the Spectro Cloud Palette console.
2. In the left-hand navigation panel, click Profiles.
3. Select the Cluster Profile that contains the following add-on packs:
   1. Splunk AppDynamics Operator and Collector
   2. OpenTelemetry Collector
4. Click the layer for the OpenTelemetry Collector. Proceed to the next section to edit the exporter section of the values file.

2. Configure Endpoint Values

The following table lists the endpoint values you can configure in the exporter section of the values file for your OpenTelemetry Collector add-on pack. These values can be used to specify whether you want to use a secure connection and the target protocol (HTTP or gRPC).

The endpoints use the Collector service in the appdynamics namespace, created by the Kubernetes and App Service Monitoring add-on packs.

To specify the protocol for the instrumentation agent, set the environment variable OTEL_EXPORTER_OTLP_PROTOCOL=<protocol>. Replace <protocol> with grpc, http/protobuf, and/or http/json. The selected transportation protocol should match the endpoint exposed by the Cisco AppDynamics Distribution of OpenTelemetry Collector. For example, gRPC should use the endpoint with port 4317 and HTTP should use the endpoint with port 4318.

In this OpenTelemetry Collector configuration example, the endpoint is configured to use an insecure connection and the gRPC protocol:

receivers:
  otlp:
    protocols:
      grpc:
      http:

processors:
  batch:

exporters:
  otlp:
    endpoint: http://appdynamics-otel-collector-service.appdynamics.svc.cluster.local:4317

extensions:
  health_check:
  pprof:
  zpages:

service:
  extensions: [health_check,pprof,zpages]
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp]
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp]
    logs:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp]

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 

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

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 

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

3. Save the Cluster Profile

Once you have modified the values file of your OpenTelemetry Collector, save the changes:

1. Click Confirm & Create. 
2. Click Save Changes.
3. Click Deploy.
   The changes will be applied to any cluster with the Cluster Profile.

Spectro Cloud® is a registered trademark of Spectro Cloud, Inc. Mention of Spectro Cloud products or services is for informational purposes only and constitutes neither an endorsement nor a recommendation of such products or services.

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