Andreas Gerstmayr

> Interestingly I get > > ``` > $ curl -s "http://localhost:44322/series/ping" > {"success":true} > ``` > > however - is the response cached (redis was running when I started...

Same with pmie in https://github.com/performancecopilot/pcp/blob/d0c53a0f9dd574cd23e22e721329e7e2d680b690/src/pmie/pmie_check.sh#L761-L766

> Notifying systemd as soon as the primary has started was intentional - we can't (and don't need to) wait for the whole farm to start during boot. If nothing...

I can't see how this issue is related to systemd? The problem is in `pmlogger_check.sh`, which is used in both systemd and non-systemd init systems. There is a condition which...

Just thinking about the impact for existing installations - pcp-zeroconf users will suddenly log metrics every 10s instead of 60s, if they have remote loggers configured and didn't set the...

> This is a bug and we should just fix it. It's not only the PMLOGGER_INTERVAL default value that's missing from the environment of non-primary loggers. +1 > re: adding...

I've added a `--with-sanitizer` option to our configure script a while back (it only supports a single value, but afaics `-fsanitize=address,undefined` also works fine. You can copy the `build/ci/platforms/fedora35-container.yml` file,...

A memory leak sanitizer would be great as well, but that'll change all timings of the QA scripts, and some will run in timeouts. Maybe we can add a new...

> We should use less of systemd/journald not more Given that systemd is the default in most popular linux distributions, I think we should strive to make the experience using...

> Actually, we could possibly do better than that and make pmdapodman behave like pmdaproc, such that it performs podman queries as the user running the client monitoring tool connected...