Skip to content

Commit 10bc512

Browse files
committed
daemonset deployment mode info added
1 parent 50f202e commit 10bc512

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -447,9 +447,9 @@ To deploy the .NET zero-code instrumentation in Kubernetes, follow these steps:
447447
spec:
448448
containers:
449449
- name: myapp
450-
env:
450+
env:
451451
- name: SPLUNK_OTEL_AGENT
452-
valueFrom:
452+
valueFrom:
453453
fieldRef:
454454
fieldPath: status.hostIP
455455
- name: OTEL_EXPORTER_OTLP_ENDPOINT
@@ -459,6 +459,7 @@ To deploy the .NET zero-code instrumentation in Kubernetes, follow these steps:
459459
- name: OTEL_RESOURCE_ATTRIBUTES
460460
value: "deployment.environment=<environmentName>"
461461
462+
Based on the collector deployment mode, modify the deployment manifest, setting the correct value for OTEL_EXPORTER_OTLP_ENDPOINT environment variable. In case of daemonset deployment mode, Kubernetes Downward API can be used to obtain an address of a collector.
462463
.. note:: You can also deploy instrumentation using the Kubernetes Operator. See :ref:`k8s-backend-auto-discovery` for more information.
463464
.. _export-directly-to-olly-cloud-dotnet-otel:
464465

0 commit comments

Comments
 (0)