Frederic Van Espen

That would be a very useful feature indeed. We have multiple elasticsearch clusters distributed in different DC's. With this feature we could point to one single elasticsearch cluster which will...

Ah, I read in the updated readme that essentially the ethernet method no longer works, only RS485 will. But does RS485 include any data about the optimizers? That's really what...

FWIW, we had the same issue establishing a connection from perl on Ubuntu jammy to an older mysql 5.1.41. Just switching to DBD::MariaDB fixed that problem for us. The libdbd-mariadb-perl...

@kgilmer any way I can help test your progress? I did the procedure above and it works, but I'd like to help out.

I suppose the progress is in the debian/bullseye branch? Can I already start testing that one?

Seeing the same problem here. Using similar config to the sample data. Works fine with older versions.

@zeritti strange. I do get the error outputs and the chart fails to install. We're using similar escaping in other charts where it works fine. Which versions of `helm` and...

Well, I don't know what to say. Myself and my colleagues all have the same problem. Other charts where we use the same syntax for alerts don't have this problem....

We can't reproduce with `helm`, but we can easily reproduce it with `helmfile` though. After troubleshooting some more, we found that we have to quote twice in order to have...

For completeness in the issue: It's these queries ```yaml --- pg_replication: query: | SELECT CASE WHEN NOT pg_is_in_recovery() THEN 0 ELSE GREATEST (0, EXTRACT(EPOCH FROM (now() - pg_last_xact_replay_timestamp()))) END AS...