[jordanbeiber]

Logging and monitoring is part of the lifecycle. Use strict automated conventions to aid developer teams. Always opt for convention before configuration is our tooling motto! :)

Log shipping is what we do from thousands of servers already (you should at least!), adding a shipper for a few 100 containers on a set of hosts is no big deal.

Fluent(d/bit) -> some kind of elastic? There are a few resonable patterns available that works and scales pretty well.

Failures and issues with the actual code - well I might have been lucky... DDD with somewhat senior devs where no spaghetti action takes place. The tooling we keep usually seem to pinpoint issues fairly well.

We’re on the scale of roughly 40 devs and my team of 3 support them with tooling that handles service lifecycle and operational stuff.

It let’s us be pretty fluent with what and how teams build and iterate stuff. I guess it requires a certain scale and experience though.