Skip to content

Commit

Permalink
Clarifications
Browse files Browse the repository at this point in the history
  • Loading branch information
aurbiztondo-splunk committed Jan 10, 2025
1 parent d670dc9 commit 8f9a37e
Show file tree
Hide file tree
Showing 4 changed files with 9 additions and 11 deletions.
6 changes: 4 additions & 2 deletions _includes/gdi/auto-discovery-intro.rst
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
Automatic discovery detects and collects signal data from third-party services, such as databases and web servers. Through auto discovery the Collector automatically generates a configuration snipet that you can modify and incorporate into your existing configuration to retrieve your services' data. Auto discovery of services is only available for the Collector in Linux and Kubernetes environments.
Automatic discovery detects and collects signal data from third-party services, such as databases and web servers. Through auto discovery the Collector automatically generates a configuration snipet that you can modify and incorporate into your existing configuration to retrieve your services' data.

With automatic discovery you can also enable zero-code instrumentation of back-end applications, which allows the Collector to retrieve data from application language runtimes without having to modify the source application code or adding any new installation or configuration steps. With this option you won't have to install and configure your instrumentation agents separately. Zero-code instrumentation using the Collector's automatic discovery feature is only available for the Java, Node.js, and .NET language runtimes. Alternatively you can deploy zero-code instrumentation independently from the Collector for 8 back-end languages, as described in :ref:`get-started-application`.
.. caution:: Auto discovery of third-party services is only available for the Collector in Linux and Kubernetes environments.

Via automatic discovery you can also enable zero-code instrumentation of back-end applications, which allows the Collector to retrieve data from application language runtimes without having to modify the source application code or adding any new installation or configuration steps. With this option you won't have to install and configure your instrumentation agents separately. Zero-code instrumentation using the Collector's automatic discovery feature is only available for the Java, Node.js, and .NET language runtimes. Alternatively you can deploy zero-code instrumentation independently from the Collector for 8 back-end languages, as described in :ref:`get-started-application`.
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Automatic discovery and zero-code instrumentation for Kubernetes

<h2>Get started</h2>

To enable the Collector's zero-code instrumentation of back-end applications written in Java, Node.js, and .NET see :ref:`k8s-backend-auto-discovery`. With this option you won't have to install and configure your instrumentation agents separately.
To enable zero-code instrumentation of Java, Node.js, and .NET applications running on Kubernetes via auto discovery see :ref:`k8s-backend-auto-discovery`. With this option you won't have to install and configure your instrumentation agents separately.

To use the Collector's automatic discovery of third-party applications in Kubernetes environments see :ref:`k8s-third-party`. With this option you'll only have to reuse a config file automatically generated by the Collector.

Expand Down
2 changes: 1 addition & 1 deletion gdi/opentelemetry/automatic-discovery/discovery-linux.rst
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Automatic discovery and zero-code instrumentation for Linux

<h2>Get started</h2>

To enable the Collector's zero-code instrumentation of back-end applications written in Java, Node.js, and .NET see :ref:`linux-backend-auto-discovery`. With this option you won't have to install and configure your instrumentation agents separately.
To enable zero-code instrumentation of Java, Node.js, and .NET applications running on Linux via auto discovery see :ref:`linux-backend-auto-discovery`. With this option you won't have to install and configure your instrumentation agents separately.

To use the Collector's automatic discovery and configuration of third-party applications in Linux environments see :ref:`linux-third-party`. With this option you'll only have to reuse a config file automatically generated by the Collector.

Expand Down
10 changes: 3 additions & 7 deletions gdi/opentelemetry/automatic-discovery/discovery-windows.rst
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,6 @@ Automatic discovery and zero-code instrumentation for Windows

Language runtimes <windows/windows-backend>



.. raw:: html

<div class="include-start" id="gdi/auto-discovery-intro.rst"></div>
Expand All @@ -24,13 +22,11 @@ Automatic discovery and zero-code instrumentation for Windows

<div class="include-stop" id="gdi/auto-discovery-intro.rst"></div>




.. raw:: html

<h2>Get started</h2>

The Collector for Windows does not support automatic discovery of third-party services.
To enable zero-code instrumentation of .NET applications running on Windows via auto discovery see :ref:`windows-backend-auto-discovery`. With this option you won't have to install and configure your instrumentation agents separately.

.. note:: The Collector for Windows does not support automatic discovery of third-party services.

To enable the Collector's zero-code instrumentation of back-end applications written in .NET see :ref:`windows-backend-auto-discovery`. With this option you won't have to install and configure your instrumentation agents separately.

0 comments on commit 8f9a37e

Please sign in to comment.