From 589488839f582632f53d84526207e733475ccc21 Mon Sep 17 00:00:00 2001 From: Pablo Baeyens Date: Wed, 27 Sep 2023 21:38:06 +0200 Subject: [PATCH] [docs] Simplify troubleshooting doc (#8554) **Description:** Remove bits mentioning configuration on versions v0.42.0 or below and versions v0.35.0 and below. These versions are more than 2 years old, and users can always switch to the docs when their version was released. --- docs/troubleshooting.md | 21 --------------------- 1 file changed, 21 deletions(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index ff51b2afb7f..b3cbe9bac5e 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -11,8 +11,6 @@ Logs can be helpful in identifying issues. Always start by checking the log output and looking for potential issues. The verbosity level defaults to `INFO` and can be adjusted. -#### Version 0.36 and above: - Set the log level in the config `service::telemetry::logs` ```yaml @@ -22,22 +20,12 @@ service: level: "debug" ``` -#### Version 0.35 and below: - -Pass `--log-level` flag to the `otelcol` process. See `--help` for more details. - -```console -$ otelcol --log-level DEBUG -``` - ### Metrics Prometheus metrics are exposed locally on port `8888` and path `/metrics`. For containerized environments it may be desirable to expose this port on a public interface instead of just locally. -#### Version 0.43.0 and above: - Set the address in the config `service::telemetry::metrics` ```yaml @@ -47,15 +35,6 @@ service: address: ":8888" ``` -#### Version 0.42.0 and below: - -Pass `--metrics-addr ` flag to the `otelcol` process. See `--help` for -more details. - -```console -$ otelcol --metrics-addr 0.0.0.0:8888 -``` - A Grafana dashboard for these metrics can be found [here](https://grafana.com/grafana/dashboards/15983-opentelemetry-collector/).