i am so hopeful that they used copilot to edit configurations live during this crisis and it made everything worse and so even if they were to fix the original problem everything will still be down because of the 10 new problems they introduced and they will never know it and it will just keep snowballing until they decide to shut everything off
@Lady Version control is where they keep the config in. Hashtag devops.
The mechanisms that AUTODEPLOY that config across the environment, tho-- now THOSE mechanisms on the other hand...
@Lady legitimately if more of our systems at my job are broken bc of this outage I will lose my mind tomorrow
@Lady and then I'll hope they gut the annoying ai stuff we have to use
@Lady Arguably it doesn't say that they know *why* the traffic rebalancing actions were taken, just that "we" took them.
@Lady I'm not saying they let a complex system get out far beyond the level anyone there can fully understand, but if they did, it probably wouldn't look all that different than this.
@Lady Yeah. They had a good explanation for this (and all the other potential problems) prepared in advance, but unfortunately they're all in Teams so they can't get to them and are just using co-pilot to one-shot it
@Lady or as my partner says "oh, it's just like their error messages! you're trying to tell me something but i have no idea what you mean. And that's why I haven't used Microsoft stuff in years!"
« We’re continuing to observe heightened volume due to traffic rebalancing actions that we have taken throughout this event. We’re working on multiple workstreams to pinpoint the underlying cause of this traffic influx and address it. » did you not just say it was due to rebalancing actions that you have taken throughout this event?