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
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: gdi/get-data-in/application/otel-dotnet/instrumentation/dotnet-pre-checks.rst
+35-9Lines changed: 35 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,16 +7,24 @@ Pre-checks
7
7
.. meta::
8
8
:description: A list of pre-checks for the user to complete before installing the .NET automatic instrumentation.
9
9
10
-
Before installing the .NET automatic instrumentation, it can be useful to complete the following series of pre-checks.
10
+
Before installing the .NET automatic instrumentation, complete the following pre-checks.
11
11
12
12
Verify platform compatibility
13
13
=============================
14
14
15
-
#. Verify that you are using a supported processor architecture. See :ref:`dotnet-otel-requirements`.
15
+
.. list-table::
16
+
:widths: 25 75
17
+
:width: 100
18
+
:header-rows: 1
16
19
17
-
#. If you are instrumenting applications in a Kubernetes cluster, verify that you are using a supported Kubernetes distribution. See :ref:`helm-chart-supported-distros`.
20
+
* - Platform
21
+
- Pre-checks
22
+
* - All platforms
23
+
- * Verify that you are using a supported processor architecture. See :ref:`dotnet-otel-requirements`.
24
+
* - Kubernetes
25
+
- * Verify that you are using a supported Kubernetes distribution. See :ref:`helm-chart-supported-distros`.
18
26
19
-
#. If you are instrumenting applications in a Kubernetes cluster, review the prerequisites and requirements for installing the instrumentation using the Helm chart. See :new-page:`Auto-instrumentation <https://github.com/signalfx/splunk-otel-collector-chart/blob/d08f989180bcb0e1ec79b63805d8951472b8d230/docs/auto-instrumentation-install.md#steps-for-setting-up-auto-instrumentation>` in the Splunk OpenTelemetry Collector for Kubernetes repository on GitHub.
27
+
* Review the prerequisites and requirements for installing the instrumentation using the Helm chart. See :new-page:`Auto-instrumentation <https://github.com/signalfx/splunk-otel-collector-chart/blob/d08f989180bcb0e1ec79b63805d8951472b8d230/docs/auto-instrumentation-install.md#steps-for-setting-up-auto-instrumentation>` in the Splunk OpenTelemetry Collector for Kubernetes repository on GitHub.
20
28
21
29
Verify .NET runtime compatibility
22
30
=================================
@@ -26,9 +34,19 @@ Verify that you are using a supported version of .NET. See :ref:`dotnet-otel-ver
26
34
Verify automatic discovery compatibility
27
35
========================================
28
36
29
-
#. If you are instrumenting applications in a Kubernetes cluster, verify automatic discovery compatibility between Kubernetes and .NET. See :ref:`k8s-backend-requirements`.
37
+
.. list-table::
38
+
:widths: 25 75
39
+
:width: 100
40
+
:header-rows: 1
30
41
31
-
#. Verify automatic discovery Windows back-end compatibility. See :ref:`windows-backend-auto-discovery`.
42
+
* - Platform
43
+
- Pre-check
44
+
* - Kubernetes
45
+
- Verify automatic discovery compatibility for Kubernetes. See :ref:`Automatic discovery and configuration for back-end applications in Kubernetes <k8s-backend-requirements>`.
46
+
* - Linux
47
+
- Verify automatic discovery compatibility for Linux. See :ref:`linux-backend-auto-discovery`.
48
+
* - Windows
49
+
- Verify automatic discovery compatibility for Windows. See :ref:`windows-backend-auto-discovery`.
32
50
33
51
Review core dependencies
34
52
========================
@@ -47,6 +65,14 @@ Review supported libraries
47
65
Verify networking requirements
48
66
==============================
49
67
50
-
#. Verify that your firewall rules allow for communication with the elected Splunk Observability Cloud instance.
51
-
52
-
#. Verify that the manager nodes have access to worker nodes on port ``9443/tcp``.
68
+
.. list-table::
69
+
:widths: 25 75
70
+
:width: 100
71
+
:header-rows: 1
72
+
73
+
* - Platform
74
+
- Pre-check
75
+
* - All platforms
76
+
- Verify that your firewall rules allow for communication with the elected Splunk Observability Cloud instance.
77
+
* - Kubernetes
78
+
- Verify that the manager nodes have access to worker nodes on port ``9443/tcp``.
0 commit comments