You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: gdi/opentelemetry/automatic-discovery/k8s/k8s-third-party.rst
+7-2
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ You can use automatic discovery to find third-party applications (such as databa
13
13
14
14
Update the Collector to version 0.94.0 and higher to activate automatic service discovery.
15
15
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.
17
17
18
18
How automatic discovery works
19
19
================================================
@@ -31,7 +31,9 @@ When running in Kubernetes, discovery mode tests bundled metric receiver configu
31
31
Deploy the Collector with automatic discovery
32
32
=================================================
33
33
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``.
35
37
36
38
The following example shows how to activate discovery mode in the Helm chart and adds authentication properties for PostgreSQL service discovery:
37
39
@@ -56,6 +58,8 @@ The following example shows how to activate discovery mode in the Helm chart and
56
58
password: '${env:POSTGRES_PASSWORD}'
57
59
tls:
58
60
insecure: true
61
+
# Activates auto discovery in UI
62
+
featureGates: splunk.continuousDiscovery
59
63
60
64
# ...
61
65
@@ -71,6 +75,7 @@ The following example shows how to activate discovery mode in the Helm chart and
71
75
secretKeyRef:
72
76
name: postgres-monitoring
73
77
key: password
78
+
74
79
75
80
To check discovery progress and statement evaluations, see the agent startup logs or use kubectl. For example:
0 commit comments