Is there a possibility that it was using Elastic before (through some logging driver) but that it defaulted to using json.log (default) logger driver now?

Looks like that there was problem with elastic search docker container. Everything was good after restarting machine.

Looks like that docker-compose down && docker-compose up flush console output. I upgraded server to 1.16.2-502, didn't had that problem before. Any idea?

I was digging around a bit, it seems that for the worker containers use default logging, that is: they use json.log files stored in /var/lib/docker/container/<hash> folders. When I do up/down of docker compose, these container folders are purged and with them my console log is gone.

Hi @<1702492411105644544:profile|YummyGrasshopper29> , console logs are saved in Elastic. I would check on the status of your container