This page covers support for Splunk AppDynamics for OpenTelemetry.

Regions and Endpoints

Please note that your OpenTelemetry data may transit through regions different from where your Controller is hosted if you configure your OpenTelemetry Collector using an Splunk AppDynamics endpoint located outside of the region where your Controller is hosted.

Region

City

Endpoint

Americas

Oregon

See SaaS Domains and IP Ranges for OpenTelemetry endpoints.

Sao Paulo

EMEA

Frankfurt

London (Coming soon)

APAC

Mumbai

Singapore

Sydney

Backend Languages

If the Flow Map displays an Unknown language icon, you may need to set the telemetry.sdk.language resource attribute to your application's language. See Set Resource Attributes to Your Application Language SDKs.

The following languages are supported for Splunk AppDynamics for OpenTelemetry:

  • *C++
  • *C#
  • Elixir
  • Erlang
  • Go
  • Java
  • JavaScript
  • Python
  • Ruby
  • Rust

*C++ and C# programming languages default to a .NET icon in the Controller UI Flow Map.

Java Agent Frameworks for OpenTelemetry

Vendor

Framework

Version

Entry Points

Exit Points

Configuration Notes

Open SourceJava Servlet API2.x, 3.0Yes--
ApacheActiveMQ5.xYesYes-
ApacheKafka Streams<=3.5.1YesYes-
ApacheApache HTTP Client-YesYesSee "HTTP Backends" on Java Backend Detection.
Open SourceHttp4s Blaze ClientBlaze versions: 0.21.1, 0.21.0, 0.20.23, 0.20.5
scala 2.11, 2.12		NoYes-
ApacheKafka0.9.0.0 to 3.0.0-YesKafka consumer entry points are disabled by default. Correlation is supported. See Apache Kafka Consumer Backends.
Open SourceMicronaut3.3.3, 3.7.4YesYes-
ApacheStruts1.x, 2.xYes-See Struts Entry Points.
ApacheTomcat5.x, 6.x, 7.x, 8.x, 9, 10Yes-See Apache Tomcat Startup Settings.
Open SourceSpring Boot2.x, 3.xYes--
Open Source

Play for Java

Play for Scala

2.3, 2.4, 2.5, 2.6, 2.7, 2.8Yes-Play EUM-APM correlation supported

Open Source

Scala2.11.6---
Open SourceSpring REST--Yes-
Open SourceSpring RMI-YesYes-
Open Source

Akka HTTP

Name: akka-http-stream-entry-enabled

Type: Boolean

Default: False

Akka Actor 2.6

Akka HTTP up to 10.2.6

Scala 2.11, 2.12

YesYes

EUM is supported

Support for Non-Route DSL

OracleWebLogic RMI9.x+YesYesSee Oracle WebLogic Startup Settings.
Oracle and BEAWebLogic Server9.x+YesYesSee Oracle WebLogic Startup Settings.
OracleOSB deployed on WebLogic12.2.1YesYesSee OSB Support.
Open SourceHTTP Client0.3-3Correlation: Yes; Entry: NoYesSee Oracle WebLogic Startup Settings and Default configuration excludes WebLogic classes.
Open SourceJava Server Pages2.x, 3.1---
Open SourceJBoss EAP7.1.5, 7.2.0, 7.3.0YesYesSee JBoss and Wildfly Startup Settings.
Open SourceJBoss Wildfly (formerly JBoss Application Server)12.x+YesYesSee JBoss and Wildfly Startup Settings.
SpringSpring Integration2.2.0+, 4.0+, 5.2, 5.3YesYes

See Spring Integration Support.

See also "Java Message Service Backends" on Java Backend Detection.

Spring WSWeb Services
(HTTP and SOAP)		3.x, 4.x, 5.xTo enable correlation using a header transported in the SOAP:Envelope set node property enable-soap-header-correlation=true-Web Service naming
Open SourceSpring WebFlux5.0, 5.1, 5.2, 5.3Spring Boot (Netty, Jetty, Tomcat, Undertow)WebClient (Reactor Netty, Reactive Jetty)

The node property enable-webclient, disables the Netty instrumentation and enables WebClient configuration.

This node property should not be enabled unless there is some issue or loss of visibility with the OOTB support. By default, the value of this property is false.

Open SourceWebSocket1.0 (Java EE 7, JSR-356)Yes, correlation
not supported		YesNode property: websocket-entry-calls-enabled

Verified OTLP Open Source Versions

Though all OTLP sources are supported, Splunk AppDynamics for OpenTelemetry has been verified to work with the following open source versions for each language:

LanguageOTLP Open Source Version
.Net, C#
  • OpenTelemetry.Exporter.OpenTelemetryProtocol: 1.2.0-rc2
  • OpenTelemetry: 1.2.0-rc2
  • Grpc.Net.Client: 2.32.0
Python
  • Python: 3.8.3
  • opentelemetry-api: 1.8.0
  • opentelemetry-exporter-otlp: 1.8.0
  • opentelemetry-exporter-otlp-proto-grpc: 1.8.0
  • opentelemetry-exporter-otlp-proto-http: 1.8.0
  • opentelemetry-instrumentation: 0.27b0
  • opentelemetry-proto: 1.8.0
  • opentelemetry-sdk: 1.8.0
  • opentelemetry-semantic-conventions: 0.27b0
Go
  • OS_NAME: Debian GNU/Linux 11 (bullseye)
  • Golang: 1.17
  • OTel: v1.4.1
C++
  • opentelemetry-cpp sdk: 1.2.0
Ruby
  • OS_NAME: "Debian GNU/Linux 10 (buster)"
  • Ruby Version: ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]
  • OTel API: 1.0.1
  • OTel SDK: 1.0.2
  • OTel OTLP Exporter: 0.21.0
Java
  • OTel Java Auto-Instrumentation: 1.29.0
JavaScript (Browser and Nodejs)

  • "@opentelemetry/api": "1.0.4"

  • "@opentelemetry/core": "1.0.1"

  • "@opentelemetry/sdk-trace-base": "1.0.1"

  • "@opentelemetry/exporter-trace-otlp-proto": "0.27.0", (export to collector)

  • "@opentelemetry/auto-instrumentations-node": "0.28.0"

  • "@opentelemetry/instrumentation" : "0.27.0"

Data Limits

See License Entitlements and Restrictions.

OpenTelemetry™ is a trademark of The Linux Foundation®.