Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit c5d31d9

Browse files
authored
Merge pull request #2268 from splunk/pw-glossary
Add glossary definitions for auto instrumentation and auto discovery
2 parents d6e23cb + a82a571 commit c5d31d9

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

references/glossary.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,12 @@ A
2323
analytics
2424
Analytics are the mathematical functions that can be applied to a collection of data points. For a full list of analytics that can be applied in Splunk Infrastructure Monitoring, see the :ref:`analytics-ref`.
2525

26+
automatic discovery
27+
Automatic discovery is a feature of the Splunk Distribution of the OpenTelemetry Collector that identifies the services, such as third-party databases and web servers, running in your environment and sends telemetry data from them to Splunk Application Performance Monitoring (APM) and Infrastructure Monitoring. The Collector configures service-specific receivers that collect data from an endpoint exposed on each service. For more information, see :ref:`discovery_mode`.
28+
29+
automatic instrumentation
30+
Automatic instrumentation allows you to instrument your applications and export telemetry data without having to modify the application source files. The language-specific instrumentation agent configures the source application to export data in a supported format to an OTLP endpoint, on either an OTLP receiver or the Splunk Observability Cloud back end. Automatic instrumentation is available for applications written in Java, Node.js, .NET, Go, Python, Ruby, and PHP and automatically collects telemetry data for code written using supported libraries in each language. For more information, see :ref:`get-started-application`.
31+
2632
C
2733
==
2834

0 commit comments

Comments
 (0)