There is still a tendency within some parts of aviation (safety auditing) to look for root causes and use tools like "fish bone diagrams" despite the more holistic approach used after an actual crash or incident.
A bunch of different services on a single status page doesn’t make it a complex system. Most of these have no relation to each other other than the high level services on the cloud providers.
No, they exist on the internet but calling them part of the same system is a bit torturous.
My toaster and the dam 1000 miles away are on the same electrical grid. Calling my toaster part of the electrical generation system because it consumes from it doesn’t make sense.
Coming back to the dashboard example, almost none of those work together to provide some kind of combined outcome you would expect from complex systems analysis (e.g. electrical generation, healthcare, etc).
If all of the boxes were ISPs instead, it would be a great example. Because they all work together to provide IP connectivity to the world and many can be down while the overall internet continues to function.
Systems span all kinds of scales. You absolutely can think of everything on the internet as a system. Same with your example of the power grid. Your toaster and dam absolutely are part of the same system.
> A bunch of different services on a single status page doesn’t make it a complex system.
you're it does not.
> Most of these have no relation to each other other than the high level services on the cloud providers.
so, some of them are related to each other? some of them even share underlying infrastructure? perhaps multiple of these are considered infrastructure for some teams?
There is still a tendency within some parts of aviation (safety auditing) to look for root causes and use tools like "fish bone diagrams" despite the more holistic approach used after an actual crash or incident.