You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For clusters with 30+ nodes or high-cardinality workloads, consider increasing the agent OTel Collector memory limit above 256 MiB.
420
452
453
+
## Monitoring with Prometheus Operator
454
+
455
+
If your cluster runs [Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator), you can create PodMonitor resources to scrape the reliability metrics components automatically.
**Note:** OBI internal metrics require two enable flags: `agent.reliabilityMetrics.obi.internalMetrics.enabled` (exposes the `/internal/metrics` endpoint) and `agent.reliabilityMetrics.obi.internalMetrics.podMonitor.enabled` (creates the PodMonitor).
467
+
468
+
### Enable All PodMonitors
469
+
470
+
Add these to your values file to enable scraping of all components:
471
+
472
+
```yaml
473
+
agent:
474
+
reliabilityMetrics:
475
+
# OBI settings
476
+
obi:
477
+
internalMetrics:
478
+
enabled: true
479
+
podMonitor:
480
+
enabled: true
481
+
labels:
482
+
release: prometheus
483
+
# Agent OTel Collector
484
+
collector:
485
+
podMonitor:
486
+
enabled: true
487
+
labels:
488
+
release: prometheus # Match your Prometheus Operator's serviceMonitorSelector
Prometheus Operator uses label selectors to decide which PodMonitors to pick up. If your Prometheus is configured with a `podMonitorSelector` (e.g., `release: prometheus`), add matching labels:
522
+
523
+
```yaml
524
+
podMonitor:
525
+
enabled: true
526
+
labels:
527
+
release: prometheus
528
+
```
529
+
530
+
To check what selector your Prometheus uses:
531
+
532
+
```bash
533
+
kubectl get prometheus -A -o jsonpath='{.items[*].spec.podMonitorSelector}'
534
+
```
535
+
536
+
An empty `podMonitorSelector` means Prometheus picks up all PodMonitors in its namespace.
0 commit comments