Site Status / System Status page

For the longest time there hasn’t been a site status page showing if there’s an issue with any of our services. For those using MyExtraneous this was done on the left hand side (as shown below)

Now we have a new, much improved version. You can find the new status site here – https://gamersarray.com/system-status

There may be some oddities with the new system as it’s extremely difficult to test “system failures” when there isn’t a failure. I will be updating the script to fix any bugs that arise.

Some may be wondering where Secondary DNS is, tomorrow it will add itself as there was a bug with my code that prevented it from being scanned.

As of posting this (Nov 28 at 6pm) there is only one date November 27th. As more and more dates are added the Uptime % (table on right) will add up to 7 days (Sunday -> Saturday), and the uptime table (at bottom) will add up to 10 days into the past.

[History] * Fixed incorrect percentages on uptime percent table (>100% or division by zero).
* Fixed Database Status not getting added.
* Changed Uptime Table to show newest date last.
! May need to look into Affected Systems when a system actually goes down as it seems like I missed a check to only pull affected systems for current day.
* Fixed Affected Systems not showing disruptions.
* Fixed Illegal String Offset for affected systems.
* Fixed Return Array not being a capital.
! Service Disruptions don’t affect downtime as they’re either confirmed maintenance or have been down for a negligible time.
* Fixed ‘orWhere’ for Affected Systems where it was ignoring the second ‘where’ statement thus showing old outages / disruptions.
* Fixed Uptime Percent Table (>100%). Variables were not being reset back to 0 for the new date.
+ Added Service Disruption to Uptime Table
* Fixed Uptime Table always showing a service was up (had small-case letter instead of capital)
* Fixed Uptime table incorrectly marking a service as down even though it was up. (set status to 0 instead of 1)
* Fixed Daily Scan not running.
* Fixed Uptime being 0% on first day of the month.
* Fixed Affected Systems showing no affected services if the service was never marked as down in cache.
+ Added Gamers Array to check list
* Fixed Gamers Array not being added to DB due to lasterror being null and not 0.
* Fixed System Status Table (bottom of page) not showing outages. Outage was being overwritten.
* Recoded Daily Downtime. This fixed Downtime always being displayed at 100% as well as the division by 0 and > 100% that was previously fixed.
* Modified Scan time to scan at the end of day to work in conjunction with Daily Downtime check.
* Modified Total Uptime to use TotalDown time to work with new scan
* Modified Daily Scan to only pull in that days information instead of pulling in all information from the month – To work with Total Uptime, Scan time and Daily Uptime percentages.
* Fixed items in DailyScan not showing Unknown status on Uptime Table. This will only fix daily scan items, anything else will still show empty spots if it doesn’t have a value. This is fixable but is difficult and too time consuming. Maybe once I re-write the display system I’ll include it. [Suggestion by Justin] * Re-coded Affected Systems. This will fix systems showing down even though they weren’t down for that day.
+ Added Maintenance
* Re-coded Disruption for an affected system being down 10 minutes or less.
* Fixed Uptime table marking items as an outage even though it was a disruption (Down for less than 10 minutes).
– Tertiary DNS is no longer counted towards downtime as there’s always DNS coverage by Primary or Secondary.