cptera

Hmm, you're right, it looks like the container `connector_healthcheck.1.r6cze5gx0o50en9a713u7h860` restarted, but the logs are still being collected after it restarted so I don't think it's an issue with docker or...

Like we deploy everything in a docker swarm and we designed our containers to restart on certain errors and in this case it restarted on an error it should have....

With the log4j bug our fix of "just using an older version" is no longer viable