Mark Nevill

Although I was thinking about server stats handler when I made the issue, the same request applies to client stats handler. In particular, because grpchan blocks context values from crossing...

@mikhailshilkov I'm running into this same issue, and I can't figure out how to proceed. With the resource defined as it was originally created, I get the import diff ```...

@mikhailshilkov thanks for the suggestion. Because I was moving resources between stacks, I ended up doing a stack export, used jq to massage the ids and then a stack import.

As an alternative, the upstream grafana chart generates a password when none is set, and documents how to fetch the generated password (https://grafana.com/docs/grafana/latest/setup-grafana/installation/helm/#access-grafana). That seems much more secure, so maybe...

@rustatian I'm probably going to have to redact some of it, is there any particular bit you're looking for?

Logs section is ```yaml logs: encoding: json level: info mode: production ```

I don't think that works for me as I want to have the http logs in general but filter out certain logs (namely successful healthcheck requests)

I'm actually having the same (or actually more of an issue, same cause but harder to mitigate) with metrics. My RR metrics now include the healthcheck traffic, which makes them...

I'm using the status plugin, but the exported metrics don't (and can't) include the HTTP URI that would be needed to filter them.

I'm sending healthcheck requests into the actual worker, to make sure the worker is able to process requests. Because these are http requests received by roadrunner and passed into the...