docs(python): Add Windows terminal examples to getting-started guide (#8875)

Signed-off-by: Pratik Mahalle <[email protected]>
Co-authored-by: Vitor Vasconcellos <[email protected]>

Author: pratik-mahalle

content/en/docs/languages/python/getting-started.md

@@ -18,6 +18,11 @@ Ensure that you have the following installed locally:
 
 - [Python 3](https://www.python.org/)
 
+> [!NOTE]
+>
+> On Windows, Python is typically invoked using `python` rather than `python3`.
+> The following examples show the correct commands for your operating system.
+
 ## Example Application
 
 The following example uses a basic [Flask](https://flask.palletsprojects.com/)
@@ -32,13 +37,26 @@ For more elaborate examples, see [examples](/docs/languages/python/examples/).
 
 To begin, set up an environment in a new directory:
 
+{{< tabpane text=true >}} {{% tab "Linux/macOS" %}}
+
 ```shell
 mkdir otel-getting-started
 cd otel-getting-started
 python3 -m venv venv
 source ./venv/bin/activate
 ```
 
+{{% /tab %}} {{% tab "Windows (PowerShell)" %}}
+
+```powershell
+mkdir otel-getting-started
+cd otel-getting-started
+python -m venv venv
+.\venv\Scripts\Activate.ps1
+```
+
+{{% /tab %}} {{< /tabpane >}}
+
 Now install Flask:
 
 ```shell
@@ -109,6 +127,8 @@ This will install Flask instrumentation.
 You can now run your instrumented app with `opentelemetry-instrument` and have
 it print to the console for now:
 
+{{< tabpane text=true >}} {{% tab "Linux/macOS" %}}
+
 ```shell
 export OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED=true
 opentelemetry-instrument \
@@ -119,6 +139,20 @@ opentelemetry-instrument \
     flask run -p 8080
 ```
 
+{{% /tab %}} {{% tab "Windows (PowerShell)" %}}
+
+```powershell
+$env:OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED="true"
+opentelemetry-instrument `
+    --traces_exporter console `
+    --metrics_exporter console `
+    --logs_exporter console `
+    --service_name dice-server `
+    flask run -p 8080
+```
+
+{{% /tab %}} {{< /tabpane >}}
+
 Open <http://localhost:8080/rolldice> in your web browser and reload the page a
 few times. After a while you should see the spans printed in the console, such
 as the following:
@@ -325,6 +359,8 @@ def roll():
 
 Now run the app again:
 
+{{< tabpane text=true >}} {{% tab "Linux/macOS" %}}
+
 ```shell
 export OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED=true
 opentelemetry-instrument \
@@ -335,6 +371,20 @@ opentelemetry-instrument \
     flask run -p 8080
 ```
 
+{{% /tab %}} {{% tab "Windows (PowerShell)" %}}
+
+```powershell
+$env:OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED="true"
+opentelemetry-instrument `
+    --traces_exporter console `
+    --metrics_exporter console `
+    --logs_exporter console `
+    --service_name dice-server `
+    flask run -p 8080
+```
+
+{{% /tab %}} {{< /tabpane >}}
+
 When you send a request to the server, you'll see two spans in the trace emitted
 to the console, and the one called `roll` registers its parent as the
 automatically created one:
@@ -472,6 +522,8 @@ def roll():
 
 Now run the app again:
 
+{{< tabpane text=true >}} {{% tab "Linux/macOS" %}}
+
 ```shell
 export OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED=true
 opentelemetry-instrument \
@@ -482,6 +534,20 @@ opentelemetry-instrument \
     flask run -p 8080
 ```
 
+{{% /tab %}} {{% tab "Windows (PowerShell)" %}}
+
+```powershell
+$env:OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED="true"
+opentelemetry-instrument `
+    --traces_exporter console `
+    --metrics_exporter console `
+    --logs_exporter console `
+    --service_name dice-server `
+    flask run -p 8080
+```
+
+{{% /tab %}} {{< /tabpane >}}
+
 When you send a request to the server, you'll see the roll counter metric
 emitted to the console, with separate counts for each roll value:
 
@@ -656,11 +722,12 @@ collector in production deployments.
 
 ### Configure and run a local collector
 
-First, save the following collector configuration code to a file in the `/tmp/`
-directory:
+First, save the following collector configuration code to a file. On
+Linux/macOS, save it to `/tmp/otel-collector-config.yaml`. On Windows, save it
+to `$env:TEMP\otel-collector-config.yaml`:
 
 ```yaml
-# /tmp/otel-collector-config.yaml
+# otel-collector-config.yaml
 receivers:
   otlp:
     protocols:
@@ -688,13 +755,26 @@ service:
 Then run the docker command to acquire and run the collector based on this
 configuration:
 
+{{< tabpane text=true >}} {{% tab "Linux/macOS" %}}
+
 ```shell
 docker run -p 4317:4317 \
     -v /tmp/otel-collector-config.yaml:/etc/otel-collector-config.yaml \
     otel/opentelemetry-collector:latest \
     --config=/etc/otel-collector-config.yaml
 ```
 
+{{% /tab %}} {{% tab "Windows (PowerShell)" %}}
+
+```powershell
+docker run -p 4317:4317 `
+    -v "${env:TEMP}\otel-collector-config.yaml:/etc/otel-collector-config.yaml" `
+    otel/opentelemetry-collector:latest `
+    --config=/etc/otel-collector-config.yaml
+```
+
+{{% /tab %}} {{< /tabpane >}}
+
 You will now have an collector instance running locally, listening on port 4317.
 
 ### Modify the command to export spans and metrics via OTLP
@@ -715,11 +795,22 @@ and default to OTLP export when it's run next.
 
 Run the application like before, but don't export to the console:
 
+{{< tabpane text=true >}} {{% tab "Linux/macOS" %}}
+
 ```shell
 export OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED=true
 opentelemetry-instrument --logs_exporter otlp flask run -p 8080
 ```
 
+{{% /tab %}} {{% tab "Windows (PowerShell)" %}}
+
+```powershell
+$env:OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED="true"
+opentelemetry-instrument --logs_exporter otlp flask run -p 8080
+```
+
+{{% /tab %}} {{< /tabpane >}}
+
 By default, `opentelemetry-instrument` exports traces and metrics over OTLP/gRPC
 and will send them to `localhost:4317`, which is what the collector is listening
 on.