3 ms·

When the cow gets sick, you shoot it.

• mschuster91 2y ago
  You still want to know why the cow got sick, in order to prevent all other cows in the stable from falling sick as well. And ideally, you want to keep the cow alive, at least if you fed it artificially.
  • bitwize 2y ago
    You're not looking at this from a DevOps perspective. In real-world cloud environments, logging into the container and expecting to have a complete Unix environment to poke around in just isn't an option. You might not even have the required permissions to do so, as a matter of corporate policy. You need to build observability directly into the application -- or you haven't built a complete cloud application.
    • Dylan16807 2y ago
      > You need to build observability directly into the application This is not objectively better than external observability. If the "DevOps perspective" requires it, then it's a pointlessly inflexible perspective. > just isn't an option You don't get to blame the system when you made the system. The option is there.
    • mschuster91 2y ago
      That's the key thing why DevOps is frankly a pile of bullshit and why so many companies ridiculously overpay on cloud infrastructure. When you got clueless morons who were in a 6 week nodejs bootcamp now "developing" containers, with no one even having the permissions to troubleshoot crashes - that may very well originate from someone trying to get remote code execution - it is absolutely no surprise that hacks, ransomware, infrastructure so brittle that it only doesn't fail because EBS / EKS keeps restarting the pile of dung every minute and infrastructure pieced together from 40 AWS services where one classic EC2 VM would be sufficient are plentiful.