Pēteris Caune

> Another one would be if the docker network is configured to be ipv6-only. Is this also your case? Is there any particular benefit of configuring docker network as ipv6-only?...

@youknow0 I did some more experimenting with this. I started Healthchecks container on my local system like so: ``` docker run \ --name=healthchecks \ -p 8000:8000 \ --restart unless-stopped \...

I was indeed running netstat on the host, but I think there's still something different between our systems. As another experiment I launched healthchecks like so: ``` docker run --rm...

Ah, managed to reproduce what you're seeing. I created ipv6-only network: ``` docker network create --ipv6 ip6net ``` Then launched the container with `--network ip6net` argument: ``` docker run --rm...

I enabled collector logs and do see the haproxy collector collecting metrics: ``` 2025-11-04 16:49:25: python.d DEBUG: haproxy[via_socket] : attempting DGRAM unix socket "/var/run/haproxy/admin.sock" 2025-11-04 16:49:25: python.d DEBUG: haproxy[via_socket] :...

Ah, oops, haproxy metrics do in fact show up in the web UI. What got me confused is that most haproxy graphs are below the netdata graphs:

Calculating how many checkins were missed has a few complications: * for cron and oncalendar schedules we would need to replay and count the missed checkin times * users can...