This message was deleted.
# general
s
This message was deleted.
👍 1
a
1. Observability - have the adequate level of alerts on logging, monitoring, but without getting alert fatigue. Only alert on really critical issues. 2. Automate as much as possible. 3. Use kubernetes and its scaling and "self healing" capabilities
👍 4
m
1. Keep change sets as small as possible 2. Double down on observability (plug for honeycomb.io)
👍 3
Note - I used honeycomb.io in my day-to-day job and do not work for them. I firmly believe they are changing the way engineers need to think about observability and making it easy to discover and be curious about your systems
👍 2