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

Commit b6829f3

Browse files
committed
Add changes from Aunsh
1 parent bd79dde commit b6829f3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

references/glossary.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,10 @@ A
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

2626
automatic discovery
27-
Automatic discovery is a feature of the Splunk Distribution of OpenTelemetry Collector that identifies the applications running in your environment and sends telemetry data from them to Splunk Application Performance Monitoring (APM). The Collector configures an application-specific receiver that collects data from an endpoint exposed on the source application. Automatic discovery is available for applications written in Java, Node.js, and .NET. For more information, see :ref:`discovery_mode`.
27+
Automatic discovery is a feature of the Splunk Distribution of the OpenTelemetry Collector that identifies the applications, 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 an application-specific receiver that collects data from an endpoint exposed on the source application. Automatic discovery is available for applications written in Java, Node.js, and .NET. For more information, see :ref:`discovery_mode`.
2828

2929
automatic instrumentation
30-
Automatic instrumentation uses an agent of the Splunk Distribution of OpenTelemetry Collector to instrument your source application and export telemetry data without requiring you to modify the application code. The 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`.
30+
Automatic instrumentation enables you to instrument your source application and export telemetry data without requiring the modification of application code. 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`.
3131

3232
C
3333
==

0 commit comments

Comments
 (0)