3 ms·
the sev1 messages in my inbox currently begs to differ. there's no issue maybe with the dns at this very moment but the platform is thoroughly fucked up
by LoSboccacc 8y ago
the sev1 messages in my inbox currently begs to differ. there's no issue maybe with the dns at this very moment but the platform is thoroughly fucked up
- solotronics 8y agoI am one of the senior Engineers and would be glad to go over anything you want to talk about if you would like me to contact you.
- LoSboccacc 8y agowell, talking would not even be cathartic, but if you want to look into the annoying things: everything is labeled severity 1. I've had three dozen of them in the last two months. only 2 of them were actually severity 1 when seen from my point of view, most of the other had impact on part of the infra I don't use or datacenter we don't have res, so filtering relevant messages would be a good start. (that's not to say the other sev 1 were mislabeled, but we keep our cloud services integration to a minimum precisely to avoid these interruption from failing dependencies.) but what is really annoying is that when one actual sev 1 that requires machine reboots happens (we had 3 in two years, so not even that bad), there's no way to manually anticipate the reboot ourselves to perform a staggered reload.