remove --unstable-otel flag from tutorials and docs (#1904)

Author: thisisjofrank

examples/tutorials/basic_opentelemetry.md

@@ -120,7 +120,7 @@ This server:
 To run the server with OpenTelemetry, use these flags:
 
 ```sh
-OTEL_DENO=true OTEL_SERVICE_NAME=my-server deno run --unstable-otel --allow-net server.ts
+OTEL_DENO=true OTEL_SERVICE_NAME=my-server deno run --allow-net server.ts
 ```
 
 ## Step 3: Create a Test Client
@@ -218,7 +218,7 @@ trace context.
 
 If you're not seeing data in your collector:
 
-1. Check that you've set `OTEL_DENO=true` and used the `--unstable-otel` flag
+1. Check that you've set `OTEL_DENO=true`
 2. Verify the collector is running and accessible at the default endpoint
 3. Check if you need to set `OTEL_EXPORTER_OTLP_ENDPOINT` to a different URL
 4. Look for errors in your Deno console output

examples/tutorials/grafana.md

@@ -185,7 +185,7 @@ to send data to the collector:
 OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318 \
 OTEL_SERVICE_NAME=chat-app \
 OTEL_DENO=true \
-deno run --unstable-otel --allow-net --allow-env --env-file --allow-read main.ts
+deno run --allow-net --allow-env --env-file --allow-read main.ts
 ```
 
 This command:

examples/tutorials/honeycomb.md

@@ -155,7 +155,7 @@ to send data to the collector:
 OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318 \
 OTEL_SERVICE_NAME=chat-app \
 OTEL_DENO=true \
-deno run --unstable-otel --allow-net --allow-env --env-file --allow-read main.ts
+deno run --allow-net --allow-env --env-file --allow-read main.ts
 ```
 
 This command:

examples/tutorials/hyperdx.md

@@ -133,7 +133,7 @@ to send data to the collector:
 OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318 \
 OTEL_SERVICE_NAME=chat-app \
 OTEL_DENO=true \
-deno run --unstable-otel --allow-net --allow-env --env-file --allow-read main.ts
+deno run --allow-net --allow-env --env-file --allow-read main.ts
 ```
 
 This command:

examples/tutorials/otel_span_propagation.md

@@ -137,14 +137,14 @@ request headers and establishes the server span as a child of the client's span.
 To run this example, first, start the server, giving your otel service a name:
 
 ```sh
-OTEL_DENO=true OTEL_SERVICE_NAME=server deno run --unstable-otel --allow-net server.ts
+OTEL_DENO=true OTEL_SERVICE_NAME=server deno run --allow-net server.ts
 ```
 
 Then, in another terminal, run the client, giving the client a different service
 name to make observing the propagation clearer:
 
 ```sh
-OTEL_DENO=true OTEL_SERVICE_NAME=client deno run --unstable-otel --allow-net client.ts
+OTEL_DENO=true OTEL_SERVICE_NAME=client deno run --allow-net client.ts
 ```
 
 You should see:

runtime/fundamentals/debugging.md

@@ -187,10 +187,8 @@ support for OpenTelemetry, allowing you to:
 - Collect structured logs
 - Export telemetry data to monitoring systems
 
-To enable OpenTelemetry, run your application with the `--unstable-otel` flag:
-
 ```sh
-OTEL_DENO=true deno run --unstable-otel your_script.ts
+OTEL_DENO=true deno run your_script.ts
 ```
 
 This will automatically collect and export runtime observability data,

runtime/fundamentals/open_telemetry.md

@@ -3,13 +3,6 @@ title: OpenTelemetry
 description: "Learn how to implement observability in Deno applications using OpenTelemetry. Covers tracing, metrics collection, and integration with monitoring systems."
 ---
 
-:::caution
-
-The OpenTelemetry integration for Deno is still in development and may change.
-To use it, you must pass the `--unstable-otel` flag to Deno.
-
-:::
-
 Deno has built in support for [OpenTelemetry](https://opentelemetry.io/).
 
 > OpenTelemetry is a collection of APIs, SDKs, and tools. Use it to instrument,
@@ -33,11 +26,11 @@ Deno provides the following features:
 
 ## Quick start
 
-To enable the OpenTelemetry integration, run your Deno script with the
-`--unstable-otel` flag and set the environment variable `OTEL_DENO=true`:
+To enable the OpenTelemetry integration set the environment variable
+`OTEL_DENO=true`:
 
 ```sh
-OTEL_DENO=true deno run --unstable-otel my_script.ts
+OTEL_DENO=true deno run my_script.ts
 ```
 
 This will automatically collect and export runtime observability data to an
@@ -270,11 +263,11 @@ In addition to the automatically collected telemetry data, you can also create
 your own metrics and traces using the `npm:@opentelemetry/api` package.
 
 You do not need to configure the `npm:@opentelemetry/api` package to use it with
-Deno. Deno sets up the `npm:@opentelemetry/api` package automatically when the
-`--unstable-otel` flag is passed. There is no need to call
-`metrics.setGlobalMeterProvider()`, `trace.setGlobalTracerProvider()`, or
-`context.setGlobalContextManager()`. All configuration of resources, exporter
-settings, etc. is done via environment variables.
+Deno. Deno sets up the `npm:@opentelemetry/api` package automatically. There is
+no need to call `metrics.setGlobalMeterProvider()`,
+`trace.setGlobalTracerProvider()`, or `context.setGlobalContextManager()`. All
+configuration of resources, exporter settings, etc. is done via environment
+variables.
 
 Deno works with version `1.x` of the `npm:@opentelemetry/api` package. You can
 either import directly from `npm:@opentelemetry/api@1`, or you can install the

runtime/reference/cli/unstable_flags.md

@@ -210,7 +210,7 @@ Enable unstable net APIs. These APIs include:
 - [`WebSocketStream`](https://developer.mozilla.org/en-US/docs/Web/API/WebSocketStream)
 - [`Deno.DatagramConn`](https://docs.deno.com/api/deno/~/Deno.DatagramConn)
 
-## `--unstable-otel`
+## ``
 
 Enable the
 [OpenTelemetry integration for Deno](/runtime/fundamentals/open_telemetry).