Configure Applications Running Inside a Supported Kubernetes Cluster

This page describes how to configure applications that are deployed in a supported Kubernetes® cluster to report OpenTelemetry™ trace data to Cisco Cloud Observability. As the diagram below illustrates, the instrumented applications send OpenTelemetry trace data to Cisco Cloud Observability via the Cisco AppDynamics Distribution of OpenTelemetry Collector.

Before You Begin

The workflows on this page assume that:

• Your applications are running in a supported cluster. See Software Requirements.
• You have installed Kubernetes and App Service Monitoring using Helm charts, which installs the Cisco AppDynamics Distribution of OpenTelemetry Collector. See Install Kubernetes and App Service Monitoring.

If either of these conditions is not true, see Configure Applications Running Outside of a Supported Kubernetes Cluster.

Configuration Workflow

Applications Not Instrumented

Auto-Instrument Your Applications

If your applications aren't instrumented with OpenTelemetry, and you are using Java, Node.js, or Python, you can leverage the OpenTelemetry Operator to auto-instrument your applications. See Auto-Instrument Your Applications using OpenTelemetry Operator for Kubernetes.

For languages not supported by auto-instrumentation, see the OpenTelemetry documentation for manual instrumentation. See Infrastructure Correlation to enable infrastructure correlation for your applications.

Applications Are Instrumented

Send Trace Data to the Cisco AppDynamics Distribution of OpenTelemetry Collector

If your applications are instrumented with OpenTelemetry, the next step is to Configure Your Applications to Send Trace Data to Cisco AppDynamics Distribution of OpenTelemetry Collector.

If you have deployed your own OpenTelemetry Collector, see Configure Your Collector to Send Trace Data to Cisco AppDynamics Distribution of OpenTelemetry Collector.

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