Skip to content
Permalink

Comparing changes

This is a direct comparison between two commits made in this repository or its related repositories. View the default comparison for this range or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: open-telemetry/opentelemetry.io
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: da40626c3f720946b7254f0d1bb82f8741ce03e8
Choose a base ref
..
head repository: open-telemetry/opentelemetry.io
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: c0176ccd18128e8375b50b11d26738f2a9dcef63
Choose a head ref
Showing with 1 addition and 1 deletion.
  1. +1 −1 content/en/docs/platforms/kubernetes/operator/troubleshooting/target-allocator.md
Original file line number Diff line number Diff line change
@@ -329,7 +329,7 @@ See the full `OpenTelemetryCollector`
### Did you configure a ServiceMonitor (or PodMonitor) selector?

If you configured a
[`ServiceMonitor`](https://observability.thomasriley.co.uk/prometheus/configuring-prometheus/using-service-monitors/)
[`ServiceMonitor`](https://observability.thomasriley.co.uk/prometheus/configuring-prometheus/using-service-monitors/#:~:text=The%20ServiceMonitor%20is%20used%20to,build%20the%20required%20Prometheus%20configuration.)
selector, it means that the Target Allocator only looks for `ServiceMonitors`
having a `metadata.label` that matches the value in
[`serviceMonitorSelector`](https://github.com/open-telemetry/opentelemetry-operator/blob/main/docs/api.md#opentelemetrycollectorspectargetallocatorprometheuscr-1).