remove otlp-promtheus content

Author: Wineshuga

content/en/docs/languages/_includes/exporters/prometheus-setup.md

@@ -1,62 +1,17 @@
 ## Prometheus
 
-To send your metric data to [Prometheus](https://prometheus.io/), you can either:
-- [Enable Prometheus' OTLP Receiver](https://prometheus.io/docs/guides/opentelemetry/#enable-the-otlp-receiver)
-and use the [OTLP exporter](#otlp) (best practice),
+To send your metric data to [Prometheus](https://prometheus.io/), you can
+either:
+
 - [Enable Prometheus' OTLP Receiver](https://prometheus.io/docs/guides/opentelemetry/#enable-the-otlp-receiver)
-and [push Prometheus to the metrics endpoint directly](#push-metrics-directly) (for development or testing purposes), or
-- Use the Prometheus exporter, a `MetricReader` that starts an HTTP server that collects metrics and serializes to Prometheus text format on request.
+  and use the [OTLP exporter](#otlp) (best practice), or
+- Use the Prometheus exporter, a `MetricReader` that starts an HTTP server that
+  collects metrics and serializes to Prometheus text format on request.
 
 ### Backend setup {#prometheus-setup}
 
-For [OTLP Exporter](#otlp-dependencies) or [Prometheus exporter](#prometheus-dependencies):
-
-  To run a Prometheus server backend and begin scraping metrics, see the [Prometheus getting started guide](https://prometheus.io/docs/prometheus/latest/getting_started/). To enable the OTLP Receiver, see the [Prometheus guide for enabling the OTLP Receiver](https://prometheus.io/docs/guides/opentelemetry/#enable-the-otlp-receiver).
-
-For pushing to a metrics endpoint directly:
-  
-  Follow the [example prometheus.yml configuration in this Prometheus guide](https://prometheus.io/docs/guides/opentelemetry/#configuring-prometheus).
-
-Once you have Prometheus set up, you can set up the OTLP Exporter, Prometheus exporter, or push to a metrics endpoint directly.
-
-### Push to metrics endpoint {#push-metrics-directly}
-This section explains how to configure your application to send metrics directly to a Prometheus endpoint.
-
-#### Use environment variables
-You can configure OpenTelemetry SDKs and instrumentation libraries with [standard environment variables](/docs/languages/sdk-configuration/). Set the environment variables before starting your application. The following OpenTelemetry variables are needed to send OpenTelemetry metrics to a Prometheus server on localhost:
-
-```bash
-export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
-export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://localhost:9090/api/v1/otlp
-```
-The OTEL_EXPORTER_OTLP_METRICS_ENDPOINT environment variable is treated as a base URL. The `/v1/metrics` path is appended as defined by the [OpenTelemetry specification](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.50.0/specification/protocol/exporter.md#endpoint-urls-for-otlphttp).
-
-Turn off traces and logs when using Prometheus if you only need metrics:
-
-```bash
-export OTEL_TRACES_EXPORTER=none
-export OTEL_LOGS_EXPORTER=none
-```
-
-The default push interval for OpenTelemetry metrics is 60 seconds. The following sets a 15-second interval for more responsive monitoring and faster alerting speed. Shorter intervals may increase network and processing overhead.
-
-```bash
-export OTEL_METRIC_EXPORT_INTERVAL=15000
-```
-
-If your instrumentation library does not provide `service.name` and `service.instance.id` out-of-the-box, it is highly recommended to set them. Without these attributes, it becomes difficult to reliably identify services or distinguish between instances, making debugging and aggregation significantly harder. The example below assumes that the `uuidgen` command is available on your system.
-
-```bash
-export OTEL_SERVICE_NAME="my-example-service"
-export OTEL_RESOURCE_ATTRIBUTES="service.instance.id=$(uuidgen)"
-```
-
-> [!NOTE]
->
-> Make sure that `service.instance.id` is unique for each instance, 
-> and that a new `service.instance.id` is generated whenever a resource attribute changes.
-> The [recommended way](/docs/specs/semconv/resource/service/#service-instance) 
-> is to generate a new UUID on each startup of an instance.
+To run a Prometheus server backend and begin scraping metrics, see the
+[Prometheus getting started guide](https://prometheus.io/docs/prometheus/latest/getting_started/).
 
-#### Configure telemetry
-Update your OpenTelemetry Configuration to use the same `exporter` and `reader` from the [OTLP](#otlp-dependencies) setup. If the environment variables are set up and loaded correctly, the OpenTelemetry SDK reads them automatically. 
+To enable the OTLP Receiver, see the
+[Prometheus guide for enabling the OTLP Receiver](https://prometheus.io/docs/guides/opentelemetry/#enable-the-otlp-receiver).