Docs » Get started with the Splunk Distribution of the OpenTelemetry Collector » Discover telemetry sources automatically

Discover telemetry sources automatically 🔗

Use automatic discovery and configuration (formerly Zero Configuration Automatic Instrumentation) with the Splunk Distribution of OpenTelemetry Collector to collect metrics and traces automatically.

Automatic discovery and configuration helps you quickly get started with Splunk Application Performance Monitoring (APM) and Splunk Infrastructure Monitoring.

The following diagram shows the process of using automatic discovery and configuration to find data sources:

flowchart LR accTitle: Automatic discovery and configuration process diagram accDescr: Step one. Connect to your cloud environment. Step two. Ensure the OpenTelemetry Collector is running. Step three. Run your application. X["Connect to your \n cloud environment"] Y["Deploy the Splunk Distribution \n of OpenTelemetry Collector \n in your environment"] Z["Run your application"] X --> Y --> Z

Automatic discovery and configuration can detect several types of data sources on the host or Kubernetes cluster, such as language runtimes, databases, and web servers.

Using this capability, you can automatically instrument your back-end applications such as Java or .NET without any additional installation or configuration steps. With automatic discovery, you can quickly get started with Splunk APM.

For third-party applications such as databases and web servers, the Collector generates configuration you can modify and adopt, or incorporate into your existing configuration automatically by default.

The main advantage of using automatic discovery is that you don’t need to manually instrument applications or manually configure the Splunk Distribution of OpenTelemetry Collector.

Supported language runtimes

The following table shows the platforms that support each language runtime:

Application language

Supported for Linux

Supported for Windows

Supported for Kubernetes

Java

Yes. See Automatic discovery and configuration for back-end applications in Linux

No

Yes. See Automatic discovery and configuration for back-end applications in Kubernetes

.NET

Yes. See Automatic discovery and configuration for back-end applications in Linux

Yes. See Automatic discovery for back-end applications in Windows

Yes. See Automatic discovery and configuration for back-end applications in Kubernetes

Node.js

Yes. See Automatic discovery and configuration for back-end applications in Linux

No

Yes. See Automatic discovery and configuration for back-end applications in Kubernetes

Supported host services and applications

Automatic discovery for third-party applications is supported for Linux and Kubernetes.

To get started with automatic discovery for third-party applications, see the instructions corresponding to your environment:

Automatic discovery supports the following host services and applications:

Service

Receiver

Apache Web Server

Apache Web Server receiver. See Apache Web Server receiver.

MySQL

MySQL receiver. See MySQL receiver

PostgreSQL

PostgreSQL receiver. See PostgreSQL receiver

OracleDB

Oracle DB receiver. See Oracle Database receiver

NGINX

Smart Agent with collectd/nginx monitor type. See NGINX

RabbitMQ

RabbitMQ receiver. See RabbitMQ receiver.

Redis

Redis receiver. See Redis receiver

MongoDB

MongoDB receiver. See MongoDB receiver

Kafka

Kafka metrics receiver. See Kafka metrics receiver

Microsoft SQL Server

Microsoft SQL Server receiver. See Microsoft SQL server receiver

This page was last updated on Nov 06, 2024.