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

Commit 9460f4a

Browse files
Fix word
1 parent 0c5a448 commit 9460f4a

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

gdi/opentelemetry/automatic-discovery/discovery-kubernetes.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,6 @@ To enable zero-code instrumentation of Java, Node.js, and .NET applications runn
3838

3939
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.
4040

41-
.. note:: If you're using the Collector version 0.109.0 or higher, log in to Splunk Observability Cloud and go to the :guilabel:`Discovered entities` tab in the :guilabel:`Data Management` menu to see which of your services and third-party applications the Collector has detected and can monitor automatically.
41+
.. note:: If you're using the Collector version 0.109.0 or higher, log in to Splunk Observability Cloud and go to the :guilabel:`Discovered services` tab in the :guilabel:`Data Management` menu to see which of your services and third-party applications the Collector has detected and can monitor automatically.
4242

4343
For a walkthrough of how to use automatic discovery and zero-code instrumentation to monitor an application in a Kubernetes environment, see :ref:`k8s-advanced-auto-discovery-config`.

gdi/opentelemetry/automatic-discovery/k8s/k8s-third-party.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ You can use automatic discovery to find third-party applications (such as databa
1313

1414
Update the Collector to version 0.94.0 and higher to activate automatic service discovery.
1515

16-
If you're using the Collector version 0.109.0 or higher, log in to Splunk Observability Cloud and go to the :guilabel:`Discovered entities` tab in the :guilabel:`Data Management` menu to see which of your services and third-party applications the Collector has detected and can monitor automatically.
16+
If you're using the Collector version 0.109.0 or higher, log in to Splunk Observability Cloud and go to the :guilabel:`Discovered services` tab in the :guilabel:`Data Management` menu to see which of your services and third-party applications the Collector has detected and can monitor automatically.
1717

1818
How automatic discovery works
1919
================================================

gdi/opentelemetry/discovery-mode.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ The following diagram shows how automatic discovery finds data sources:
5252

5353
<h2>Supported host services and applications for automatic discovery</h2>
5454

55-
.. note:: If you're in a Kubernetes environment and are using the Collector version 0.109.0 or higher, log in to Splunk Observability Cloud and go to the :guilabel:`Discovered entities` tab in the :guilabel:`Data Management` menu to see which of your services and third-party applications the Collector has detected and can monitor automatically.
55+
.. note:: If you're in a Kubernetes environment and are using the Collector version 0.109.0 or higher, log in to Splunk Observability Cloud and go to the :guilabel:`Discovered services` tab in the :guilabel:`Data Management` menu to see which of your services and third-party applications the Collector has detected and can monitor automatically.
5656

5757
Automatic discovery of third-party applications is supported in Linux and Kubernetes environments for the following services:
5858

0 commit comments

Comments
 (0)