Skip to content

Commit

Permalink
[docs] Simplify troubleshooting doc (#8554)
Browse files Browse the repository at this point in the history
**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.
  • Loading branch information
mx-psi authored Sep 27, 2023
1 parent d77d2c2 commit 5894888
Showing 1 changed file with 0 additions and 21 deletions.
21 changes: 0 additions & 21 deletions docs/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand All @@ -47,15 +35,6 @@ service:
address: ":8888"
```

#### Version 0.42.0 and below:

Pass `--metrics-addr <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/).

Expand Down

0 comments on commit 5894888

Please sign in to comment.