Great writeup, have definitely been bit by container_memory_working_set_bytes before - in fact when I first read the description of the dashboard I was wonderin

Great writeup, have definitely been bit by container_memory_working_set_bytes before - in fact when I first read the description of the dashboard I was wondering if it was something like that. This is one of the most difficult parts of working in SRE or DevOps, often each side of the conversation lacks the necessary context to understand what the problem is. As author mentioned, this is still a worthwhile metric to monitor, but its meaning is not necessarily clear in this context. Kudos to this author for digging in - as a DevOps/SRE guy, I'd imagine this conversation often going in companies I have worked for like "Something is wrong with your dashboard" and my team being like "something is wrong with your application" and nothing gets done for months while managers point fingers and figure out whose problem it is.