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
Fix Grafana dashboards for Broker with honorLabels, remove unnecessary *_created metrics and improve docs (#593)
* Drop _created metrics for broker and proxy
* Enable all metrics by default for broker
* change default dashboard
* Remove messy dashboards
* Enable default dashboards in Grafana
* Add testing values with more aggressive disk cleanup
* Add VictoriaMetrics debugging instructions
* Set honorLabels to true
* Document disabling monitoring
* Set password in testing values
* Fix linting issue detected by kubeconform
Copy file name to clipboardExpand all lines: README.md
+64-4Lines changed: 64 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -280,23 +280,53 @@ You can also checkout out the example values file for different deployments.
280
280
281
281
In order to disable the victoria-metrics-k8s-stack, you can add the following to your `values.yaml`.
282
282
Victoria Metrics components can also be disabled and enabled individually if you only need specific monitoring features.
283
-
Please refer to the default [`values.yaml`](charts/pulsar/values.yaml).
284
283
285
284
```yaml
285
+
# disable VictoriaMetrics and related components
286
286
victoria-metrics-k8s-stack:
287
287
enabled: false
288
288
victoria-metrics-operator:
289
289
enabled: false
290
+
vmsingle:
291
+
enabled: false
292
+
vmagent:
293
+
enabled: false
290
294
kube-state-metrics:
291
295
enabled: false
292
296
prometheus-node-exporter:
293
297
enabled: false
294
298
grafana:
295
299
enabled: false
300
+
301
+
Additionally, you'll need to set each component's `podMonitor` property to `false`.
302
+
303
+
```yaml
304
+
# disable pod monitors
305
+
autorecovery:
306
+
podMonitor:
307
+
enabled: false
308
+
bookkeeper:
309
+
podMonitor:
310
+
enabled: false
311
+
oxia:
312
+
server:
313
+
podMonitor:
314
+
enabled: false
315
+
coordinator:
316
+
podMonitor:
317
+
enabled: false
318
+
broker:
319
+
podMonitor:
320
+
enabled: false
321
+
proxy:
322
+
podMonitor:
323
+
enabled: false
324
+
zookeeper:
325
+
podMonitor:
326
+
enabled: false
296
327
```
297
328
298
-
Additionally, you'll need to set each component's `podMonitor` property to `false`. This is shown in some [examples](./examples) and is
299
-
verified in some [tests](./.ci/clusters).
329
+
This is shown in some [examples/values-disable-monitoring.yaml](examples/values-disable-monitoring.yaml).
300
330
301
331
## Pulsar Manager
302
332
@@ -497,6 +527,36 @@ We've done our best to make these charts as seamless as possible,
497
527
occasionally troubles do surface outside of our control. We've collected
498
528
tips and tricks for troubleshooting common issues. Please examine these first before raising an [issue](https://github.com/apache/pulsar-helm-chart/issues/new/choose), and feel free to add to them by raising a [Pull Request](https://github.com/apache/pulsar-helm-chart/compare)!
499
529
530
+
### VictoriaMetrics Troubleshooting
531
+
532
+
In example commands, k8s is namespace `pulsar` replace with your deployment namespace.
0 commit comments