Skip to content

Commit 48902c3

Browse files
Merge pull request #2594 from splunk/urbiz-OD6528-ad-ui
[6528]: Activate AD in UI
2 parents 5d114b9 + 709e3f4 commit 48902c3

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

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

+7-2
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 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.
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. See :ref:`discovery-mode-k8s` for more details.
1717

1818
How automatic discovery works
1919
================================================
@@ -31,7 +31,9 @@ When running in Kubernetes, discovery mode tests bundled metric receiver configu
3131
Deploy the Collector with automatic discovery
3232
=================================================
3333

34-
You can configure the DaemonSet from the Splunk Distribution of OpenTelemetry Collector for Kubernetes to run in discovery mode. Edit the properties to add required credentials or service-specific information.
34+
You can configure the DaemonSet from the Splunk Distribution of the OpenTelemetry Collector for Kubernetes to run in discovery mode. Edit the properties to add required credentials or service-specific information.
35+
36+
.. note:: If you're using the Collector version 0.109.0 or higher, activate auto-discovery in the UI using ``featureGates: splunk.continuousDiscovery``.
3537

3638
The following example shows how to activate discovery mode in the Helm chart and adds authentication properties for PostgreSQL service discovery:
3739

@@ -56,6 +58,8 @@ The following example shows how to activate discovery mode in the Helm chart and
5658
password: '${env:POSTGRES_PASSWORD}'
5759
tls:
5860
insecure: true
61+
# Activates auto discovery in UI
62+
featureGates: splunk.continuousDiscovery
5963
6064
# ...
6165
@@ -71,6 +75,7 @@ The following example shows how to activate discovery mode in the Helm chart and
7175
secretKeyRef:
7276
name: postgres-monitoring
7377
key: password
78+
7479
7580
To check discovery progress and statement evaluations, see the agent startup logs or use kubectl. For example:
7681

0 commit comments

Comments
 (0)