From 63afe5ac36d57534cebd7efa07fb6f736660c521 Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 4 Apr 2025 10:15:44 +0200 Subject: [PATCH 01/16] Deploy the .NET agent in Kubernetes added --- .../instrument-dotnet-application.rst | 45 +++++++++++++++++++ 1 file changed, 45 insertions(+) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index e3c6d005f..43c6167ca 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -404,6 +404,51 @@ To install the .NET zero-code instrumentation on Windows hosts that are offline, Install-OpenTelemetryCore -LocalPath "C:\Users\Administrator\Downloads\splunk-opentelemetry-dotnet-windows.zip" + +Deploy the .NET agent in Kubernetes +==================================================================== + +To deploy the .NET agent in Kubernetes, follow these steps: + +#. Create a Docker image useing the instructions for creating a NuGet package for Linux or Windows. +Refer to :ref:`otel-dotnet-nuget-pkg`. + +#. Modify the Entrypoint to adjust it to call the appropriate script based on your operating system: +For Linux: +.. code-block:: powershell + splunk-launch.sh dotnet . +For Windows: +.. code-block:: powershell + splunk-launch.cmd dotnet . + +#. Configure the Kubernetes Downward API to expose environment variables to Kubernetes resources. +The following example demonstrates how to update a deployment to expose environment variables by adding the agent configuration under the ``.spec.template.spec.containers.env`` section: +.. code-block:: yaml + + apiVersion: apps/v1 + kind: Deployment + spec: + selector: + matchLabels: + app: your-application + template: + spec: + containers: + - name: myapp + env: + - name: SPLUNK_OTEL_AGENT + valueFrom: + fieldRef: + fieldPath: status.hostIP + - name: OTEL_EXPORTER_OTLP_ENDPOINT + value: "http://$(SPLUNK_OTEL_AGENT):4318" + - name: OTEL_SERVICE_NAME + value: "" + - name: OTEL_RESOURCE_ATTRIBUTES + value: "deployment.environment=" + +.. note:: You can also deploy instrumentation using the Kubernetes Operator. See :ref:`k8s-backend-auto-discovery` for more information. + .. _export-directly-to-olly-cloud-dotnet-otel: Send data directly to Splunk Observability Cloud From 3d0b52b3ef8e2f1bb06e617340e80499602fa2af Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 4 Apr 2025 10:24:45 +0200 Subject: [PATCH 02/16] fixing errors --- .../instrumentation/instrument-dotnet-application.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index 43c6167ca..c794a26d7 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -415,14 +415,17 @@ Refer to :ref:`otel-dotnet-nuget-pkg`. #. Modify the Entrypoint to adjust it to call the appropriate script based on your operating system: For Linux: + .. code-block:: powershell splunk-launch.sh dotnet . + For Windows: + .. code-block:: powershell splunk-launch.cmd dotnet . -#. Configure the Kubernetes Downward API to expose environment variables to Kubernetes resources. -The following example demonstrates how to update a deployment to expose environment variables by adding the agent configuration under the ``.spec.template.spec.containers.env`` section: +#. Configure the Kubernetes Downward API to expose environment variables to Kubernetes resources. The following example demonstrates how to update a deployment to expose environment variables by adding the agent configuration under the ``.spec.template.spec.containers.env`` section: + .. code-block:: yaml apiVersion: apps/v1 From b15ad391a613b3b3938af8dd845826ab65b7a674 Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 4 Apr 2025 10:30:01 +0200 Subject: [PATCH 03/16] structure update --- .../instrument-dotnet-application.rst | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index c794a26d7..7da6c8cbd 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -411,22 +411,24 @@ Deploy the .NET agent in Kubernetes To deploy the .NET agent in Kubernetes, follow these steps: #. Create a Docker image useing the instructions for creating a NuGet package for Linux or Windows. -Refer to :ref:`otel-dotnet-nuget-pkg`. + Refer to :ref:`otel-dotnet-nuget-pkg`. #. Modify the Entrypoint to adjust it to call the appropriate script based on your operating system: -For Linux: + For Linux: + + .. code-block:: powershell -.. code-block:: powershell splunk-launch.sh dotnet . -For Windows: + For Windows: -.. code-block:: powershell + .. code-block:: powershell + splunk-launch.cmd dotnet . #. Configure the Kubernetes Downward API to expose environment variables to Kubernetes resources. The following example demonstrates how to update a deployment to expose environment variables by adding the agent configuration under the ``.spec.template.spec.containers.env`` section: -.. code-block:: yaml + .. code-block:: yaml apiVersion: apps/v1 kind: Deployment From bcb722c055dc9869e6cf5be8ab5560ad20793176 Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 4 Apr 2025 10:42:16 +0200 Subject: [PATCH 04/16] minor changes --- .../instrumentation/instrument-dotnet-application.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index 7da6c8cbd..1d643721d 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -414,16 +414,17 @@ To deploy the .NET agent in Kubernetes, follow these steps: Refer to :ref:`otel-dotnet-nuget-pkg`. #. Modify the Entrypoint to adjust it to call the appropriate script based on your operating system: - For Linux: + + **For Linux:** .. code-block:: powershell splunk-launch.sh dotnet . - For Windows: + **For Windows:** .. code-block:: powershell - + splunk-launch.cmd dotnet . #. Configure the Kubernetes Downward API to expose environment variables to Kubernetes resources. The following example demonstrates how to update a deployment to expose environment variables by adding the agent configuration under the ``.spec.template.spec.containers.env`` section: @@ -453,7 +454,6 @@ To deploy the .NET agent in Kubernetes, follow these steps: value: "deployment.environment=" .. note:: You can also deploy instrumentation using the Kubernetes Operator. See :ref:`k8s-backend-auto-discovery` for more information. - .. _export-directly-to-olly-cloud-dotnet-otel: Send data directly to Splunk Observability Cloud From 8cd5a878059b8ca4d5eb2014d2d671395df379f7 Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 4 Apr 2025 11:08:04 +0200 Subject: [PATCH 05/16] example added --- .../instrument-dotnet-application.rst | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index 1d643721d..bf2598140 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -414,19 +414,25 @@ To deploy the .NET agent in Kubernetes, follow these steps: Refer to :ref:`otel-dotnet-nuget-pkg`. #. Modify the Entrypoint to adjust it to call the appropriate script based on your operating system: - + **For Linux:** - .. code-block:: powershell + .. code-block:: docker splunk-launch.sh dotnet . **For Windows:** - .. code-block:: powershell + .. code-block:: docker splunk-launch.cmd dotnet . + Example: + + .. code-block:: docker + + ENTRYPOINT ["./splunk-launch.sh", "dotnet", "myapp.dll"] + #. Configure the Kubernetes Downward API to expose environment variables to Kubernetes resources. The following example demonstrates how to update a deployment to expose environment variables by adding the agent configuration under the ``.spec.template.spec.containers.env`` section: .. code-block:: yaml From 130825ac6d55c27b00b5f1e4975f369789cac82e Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 4 Apr 2025 14:37:24 +0200 Subject: [PATCH 06/16] comments applied --- .../instrument-dotnet-application.rst | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index bf2598140..965d0e937 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -410,7 +410,7 @@ Deploy the .NET agent in Kubernetes To deploy the .NET agent in Kubernetes, follow these steps: -#. Create a Docker image useing the instructions for creating a NuGet package for Linux or Windows. +#. Build a Docker image by following the instructions for configuring instrumentation with the NuGet package for Linux or Windows. Refer to :ref:`otel-dotnet-nuget-pkg`. #. Modify the Entrypoint to adjust it to call the appropriate script based on your operating system: @@ -440,18 +440,18 @@ To deploy the .NET agent in Kubernetes, follow these steps: apiVersion: apps/v1 kind: Deployment spec: - selector: - matchLabels: - app: your-application - template: - spec: - containers: - - name: myapp - env: + selector: + matchLabels: + app: your-application + template: + spec: + containers: + - name: myapp + env: - name: SPLUNK_OTEL_AGENT - valueFrom: - fieldRef: - fieldPath: status.hostIP + valueFrom: + fieldRef: + fieldPath: status.hostIP - name: OTEL_EXPORTER_OTLP_ENDPOINT value: "http://$(SPLUNK_OTEL_AGENT):4318" - name: OTEL_SERVICE_NAME From d40fd8eacf2dfde786205159da8f890c16b6f27e Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 4 Apr 2025 14:46:38 +0200 Subject: [PATCH 07/16] indent changed --- .../instrumentation/instrument-dotnet-application.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index 965d0e937..e499b2498 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -453,11 +453,11 @@ To deploy the .NET agent in Kubernetes, follow these steps: fieldRef: fieldPath: status.hostIP - name: OTEL_EXPORTER_OTLP_ENDPOINT - value: "http://$(SPLUNK_OTEL_AGENT):4318" + value: "http://$(SPLUNK_OTEL_AGENT):4318" - name: OTEL_SERVICE_NAME - value: "" + value: "" - name: OTEL_RESOURCE_ATTRIBUTES - value: "deployment.environment=" + value: "deployment.environment=" .. note:: You can also deploy instrumentation using the Kubernetes Operator. See :ref:`k8s-backend-auto-discovery` for more information. .. _export-directly-to-olly-cloud-dotnet-otel: From 4d93aed01d31f34da79a54d0dc8a2c7434958143 Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 4 Apr 2025 14:56:35 +0200 Subject: [PATCH 08/16] new version of code paste --- .../instrument-dotnet-application.rst | 44 +++++++++---------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index e499b2498..f61a3eabe 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -436,28 +436,28 @@ To deploy the .NET agent in Kubernetes, follow these steps: #. Configure the Kubernetes Downward API to expose environment variables to Kubernetes resources. The following example demonstrates how to update a deployment to expose environment variables by adding the agent configuration under the ``.spec.template.spec.containers.env`` section: .. code-block:: yaml - - apiVersion: apps/v1 - kind: Deployment - spec: - selector: - matchLabels: - app: your-application - template: - spec: - containers: - - name: myapp - env: - - name: SPLUNK_OTEL_AGENT - valueFrom: - fieldRef: - fieldPath: status.hostIP - - name: OTEL_EXPORTER_OTLP_ENDPOINT - value: "http://$(SPLUNK_OTEL_AGENT):4318" - - name: OTEL_SERVICE_NAME - value: "" - - name: OTEL_RESOURCE_ATTRIBUTES - value: "deployment.environment=" + +apiVersion: apps/v1 +kind: Deployment +spec: + selector: + matchLabels: + app: your-application + template: + spec: + containers: + - name: myapp + env: + - name: SPLUNK_OTEL_AGENT + valueFrom: + fieldRef: + fieldPath: status.hostIP + - name: OTEL_EXPORTER_OTLP_ENDPOINT + value: "http://$(SPLUNK_OTEL_AGENT):4318" + - name: OTEL_SERVICE_NAME + value: "" + - name: OTEL_RESOURCE_ATTRIBUTES + value: "deployment.environment=" .. note:: You can also deploy instrumentation using the Kubernetes Operator. See :ref:`k8s-backend-auto-discovery` for more information. .. _export-directly-to-olly-cloud-dotnet-otel: From 7459af455ede506e7bb891b96bf580b072d8c691 Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 4 Apr 2025 15:05:13 +0200 Subject: [PATCH 09/16] code sample fixed --- .../instrument-dotnet-application.rst | 44 +++++++++---------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index f61a3eabe..7f856c6e5 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -436,28 +436,28 @@ To deploy the .NET agent in Kubernetes, follow these steps: #. Configure the Kubernetes Downward API to expose environment variables to Kubernetes resources. The following example demonstrates how to update a deployment to expose environment variables by adding the agent configuration under the ``.spec.template.spec.containers.env`` section: .. code-block:: yaml - -apiVersion: apps/v1 -kind: Deployment -spec: - selector: - matchLabels: - app: your-application - template: - spec: - containers: - - name: myapp - env: - - name: SPLUNK_OTEL_AGENT - valueFrom: - fieldRef: - fieldPath: status.hostIP - - name: OTEL_EXPORTER_OTLP_ENDPOINT - value: "http://$(SPLUNK_OTEL_AGENT):4318" - - name: OTEL_SERVICE_NAME - value: "" - - name: OTEL_RESOURCE_ATTRIBUTES - value: "deployment.environment=" + + apiVersion: apps/v1 + kind: Deployment + spec: + selector: + matchLabels: + app: your-application + template: + spec: + containers: + - name: myapp + env: + - name: SPLUNK_OTEL_AGENT + valueFrom: + fieldRef: + fieldPath: status.hostIP + - name: OTEL_EXPORTER_OTLP_ENDPOINT + value: "http://$(SPLUNK_OTEL_AGENT):4318" + - name: OTEL_SERVICE_NAME + value: "" + - name: OTEL_RESOURCE_ATTRIBUTES + value: "deployment.environment=" .. note:: You can also deploy instrumentation using the Kubernetes Operator. See :ref:`k8s-backend-auto-discovery` for more information. .. _export-directly-to-olly-cloud-dotnet-otel: From a3a14a1b4ae969e51d65a3adc9fd69350ef9a355 Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 4 Apr 2025 15:15:27 +0200 Subject: [PATCH 10/16] final version --- .../instrument-dotnet-application.rst | 43 +++++++++---------- 1 file changed, 21 insertions(+), 22 deletions(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index 7f856c6e5..771eb907d 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -436,28 +436,27 @@ To deploy the .NET agent in Kubernetes, follow these steps: #. Configure the Kubernetes Downward API to expose environment variables to Kubernetes resources. The following example demonstrates how to update a deployment to expose environment variables by adding the agent configuration under the ``.spec.template.spec.containers.env`` section: .. code-block:: yaml - - apiVersion: apps/v1 - kind: Deployment - spec: - selector: - matchLabels: - app: your-application - template: - spec: - containers: - - name: myapp - env: - - name: SPLUNK_OTEL_AGENT - valueFrom: - fieldRef: - fieldPath: status.hostIP - - name: OTEL_EXPORTER_OTLP_ENDPOINT - value: "http://$(SPLUNK_OTEL_AGENT):4318" - - name: OTEL_SERVICE_NAME - value: "" - - name: OTEL_RESOURCE_ATTRIBUTES - value: "deployment.environment=" + apiVersion: apps/v1 + kind: Deployment + spec: + selector: + matchLabels: + app: your-application + template: + spec: + containers: + - name: myapp + env: + - name: SPLUNK_OTEL_AGENT + valueFrom: + fieldRef: + fieldPath: status.hostIP + - name: OTEL_EXPORTER_OTLP_ENDPOINT + value: "http://$(SPLUNK_OTEL_AGENT):4318" + - name: OTEL_SERVICE_NAME + value: "" + - name: OTEL_RESOURCE_ATTRIBUTES + value: "deployment.environment=" .. note:: You can also deploy instrumentation using the Kubernetes Operator. See :ref:`k8s-backend-auto-discovery` for more information. .. _export-directly-to-olly-cloud-dotnet-otel: From 2edf449381349594513129019d0b6bc310587bdc Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 4 Apr 2025 15:25:09 +0200 Subject: [PATCH 11/16] fixed --- .../instrumentation/instrument-dotnet-application.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index 771eb907d..809b142ec 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -436,6 +436,7 @@ To deploy the .NET agent in Kubernetes, follow these steps: #. Configure the Kubernetes Downward API to expose environment variables to Kubernetes resources. The following example demonstrates how to update a deployment to expose environment variables by adding the agent configuration under the ``.spec.template.spec.containers.env`` section: .. code-block:: yaml + apiVersion: apps/v1 kind: Deployment spec: From 50f202e98251b63469acc57e059a99732a50b3b1 Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Mon, 7 Apr 2025 09:02:07 +0200 Subject: [PATCH 12/16] title update --- .../instrumentation/instrument-dotnet-application.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index 809b142ec..2ad311d34 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -405,10 +405,10 @@ To install the .NET zero-code instrumentation on Windows hosts that are offline, Install-OpenTelemetryCore -LocalPath "C:\Users\Administrator\Downloads\splunk-opentelemetry-dotnet-windows.zip" -Deploy the .NET agent in Kubernetes -==================================================================== +Deploy the .NET zero-code instrumentation in Kubernetes +---------------------------------------------- -To deploy the .NET agent in Kubernetes, follow these steps: +To deploy the .NET zero-code instrumentation in Kubernetes, follow these steps: #. Build a Docker image by following the instructions for configuring instrumentation with the NuGet package for Linux or Windows. Refer to :ref:`otel-dotnet-nuget-pkg`. @@ -417,13 +417,13 @@ To deploy the .NET agent in Kubernetes, follow these steps: **For Linux:** - .. code-block:: docker + .. code-block:: shell splunk-launch.sh dotnet . **For Windows:** - .. code-block:: docker + .. code-block:: powershell splunk-launch.cmd dotnet . From 10bc512389139d591805abe2a8d39df16c4e9758 Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 25 Apr 2025 11:35:57 +0200 Subject: [PATCH 13/16] daemonset deployment mode info added --- .../instrumentation/instrument-dotnet-application.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index 2ad311d34..cd4192cb3 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -447,9 +447,9 @@ To deploy the .NET zero-code instrumentation in Kubernetes, follow these steps: spec: containers: - name: myapp - env: + env: - name: SPLUNK_OTEL_AGENT - valueFrom: + valueFrom: fieldRef: fieldPath: status.hostIP - name: OTEL_EXPORTER_OTLP_ENDPOINT @@ -459,6 +459,7 @@ To deploy the .NET zero-code instrumentation in Kubernetes, follow these steps: - name: OTEL_RESOURCE_ATTRIBUTES value: "deployment.environment=" +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. .. note:: You can also deploy instrumentation using the Kubernetes Operator. See :ref:`k8s-backend-auto-discovery` for more information. .. _export-directly-to-olly-cloud-dotnet-otel: From 27c94e00e36e04853f3eb8527704cdae3d784848 Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 25 Apr 2025 11:38:45 +0200 Subject: [PATCH 14/16] daemonset deployment mode info added --- .../instrumentation/instrument-dotnet-application.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index cd4192cb3..7b7a43c45 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -406,7 +406,7 @@ To install the .NET zero-code instrumentation on Windows hosts that are offline, Deploy the .NET zero-code instrumentation in Kubernetes ----------------------------------------------- +---------------------------------------------------------- To deploy the .NET zero-code instrumentation in Kubernetes, follow these steps: From 5379c557551b3d1527ae4fac36598b44a92dea8a Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 25 Apr 2025 11:47:07 +0200 Subject: [PATCH 15/16] daemonset deployment mode - info added --- .../instrumentation/instrument-dotnet-application.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index 7b7a43c45..60344c9a8 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -460,6 +460,7 @@ To deploy the .NET zero-code instrumentation in Kubernetes, follow these steps: value: "deployment.environment=" 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. + .. note:: You can also deploy instrumentation using the Kubernetes Operator. See :ref:`k8s-backend-auto-discovery` for more information. .. _export-directly-to-olly-cloud-dotnet-otel: From 4f5e60f2fe761fcbca2dc00cddf459745a7761f1 Mon Sep 17 00:00:00 2001 From: pkopta-splunk Date: Fri, 25 Apr 2025 12:45:14 +0200 Subject: [PATCH 16/16] Anna's comments applied --- .../instrumentation/instrument-dotnet-application.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst index 60344c9a8..11ca81563 100644 --- a/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst +++ b/gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst @@ -459,7 +459,7 @@ To deploy the .NET zero-code instrumentation in Kubernetes, follow these steps: - name: OTEL_RESOURCE_ATTRIBUTES value: "deployment.environment=" -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. +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. .. note:: You can also deploy instrumentation using the Kubernetes Operator. See :ref:`k8s-backend-auto-discovery` for more information. .. _export-directly-to-olly-cloud-dotnet-otel: