danderson, fwiw, I think their systems were working, and the monitoring page seems to display systems. What was wrong was a bug, and for my organization, we would represent that as a ‘major incident’ and expose major incidents on the same page as system information. Not sure if that would solve what you are talking about. I am personally glad that their systems did not go down, even though I would have appreciated knowing they were aware of a large scale ‘major incident’ affecting some readings.
You’re highlighting an interesting challenge. This particular problem was an “app issue” as opposed to an operational issue in the cloud data collection and analysis systems. status.sense.com is built to show the status of the data collection and analysis systems. But it would be nice to have widespread app issues be flagged there as well.
exactly, its a major incident with rca due to bug, what you suggested is exactly what I meant and would classify it the same.
If a customer cant see/use the product its still an outage, regardless if the collection part was fine.
I also think as @kevin1 stated their status page is just not reflecting all aspects of their product, and only cover collection and analysis , I would say they need to add the application layer in it as well.
The solar graph display issue that waa reported here has been resolved. It was a simple display issue that should not have affected your data.
The issue was resolved on Friday, September 29, 2023, at around 3 PM Eastern Daylight time.
I first became aware of the issue on Thursday, September 28, 2023, and it may have affected users as early as the day before. Since the issue was resolved fairly quickly, you should have only been affected for a short period of time.
Thanks again for your patience have a great rest of the day!
Also, I just wanted you to know with the “outages” page, I hear you, and I will suggest this feedback and see what we can do. We have several systems to handle these issues in different places - including here.
I’ll advocate for you @danderson, and others. I appreciate the concern and would be glad to see what I can do with it. Please note, though, that it’s not just me who makes these decisions!
Thanks again! I’m always glad to help.
Moment I posted about:
moment you posted it was solved in my time zone:
1 day 4 hours.
It is obvious I have a different definition of “affected for a short period of time”
@dannyterhaar That is understandable, and I can understand. But for the amount of time for us to see the bug, recognize it, and get the resources on to work on it and fix it, It seemed pretty quick. Also, granted, this was a display issue, so no data was lost or being lost during this time.