This page describes how Spectro Cloud® Palette users can configure services that are deployed in a supported Kubernetes® cluster to report OpenTelemetry™ trace data to Cisco Cloud Observability.

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.

Before You Begin

The workflows on this page assume that:

Configuration Workflow

Services Not Instrumented

Auto-Instrument Your Services

If your services aren't instrumented with OpenTelemetry, and you are using Java, Node.js, or Python, you can leverage the OpenTelemetry Operator to auto-instrument your services. See Auto-Instrument Your Services with OpenTelemetry Operator on Spectro Cloud Palette.

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

Services Are Instrumented

Send Trace Data to the 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 Using Spectro Cloud Palette.

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®.