Lari Hotari

Great work @shustsud . I hope @graysonzeng could also review this PR. Perhaps not directly related to this issue, but what's your thoughts on the logic in sendAddSuccessCallbacks: https://github.com/apache/bookkeeper/blob/13e7efaa971cd3613b065ac50836c5ee98985d13/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerHandle.java#L1822-L1829 Why...

This might be caused by the configured authentication. I guess metrics requires a token currently.

for the broker `authenticateMetricsEndpoint` defaults to false, so it might be something else.

> I was having the same issue. Could resolve it by installing the helm chart into 'default' namespace rather than 'pulsar' thanks, @lerodu. Most likely this could be resolved by...

> > I was having the same issue. Could resolve it by installing the helm chart into 'default' namespace rather than 'pulsar' > > thanks, @lerodu. Most likely this could...

It seems that this problem will be solved in the helm chart release 4.0.0 where #555 is also addressed. If you'd like to use an existing Prometheus instance which isn't...

One detail is that Helm's `--namespace`/`-n` option should be used to set the namespace for the Pulsar deployment, including the kube-prometheus-stack deployment. The Pulsar Helm chart currently only supports a...

Reopening this issue since the dashboards don't connect to the datasource and that causes a problem.

Looks like this part should take care of adjusting the datasource https://github.com/grafana/helm-charts/blob/41e990ef5498feb7fd79c49d319675463c4a0f9f/charts/grafana/templates/_config.tpl#L122-L130

@danielnesaraj `msgBacklog` is currently an estimated value as described in #6045, perhaps docs should explain this too. If you need accurate values, there's `--get-precise-backlog` option for topic stats and `exposePreciseBacklogInPrometheus=true`...