SEVERELY ERRORED SECONDS AVAILABLE!This data hasn't been available until now since the data isn't uploaded in the usual format. It's now calculated and stored on MDWS locally though and has been available for a few days. Examples attached.
Available only in Wide graph format and limited to the Current Date/Time range. It function pretty much the same way as Errored Seconds, with data being updated every hours at 3 minutes past the hour. Data is available back about two months currently. The entry appears immediately after Errored Seconds in the dropdown list as
Severely ES.
The Status bar (which shows the current minute's instantaneous figures) above the graphs also shows SES adjacent to ES. To help spot any, the SES section takes on a coloured background when any are detected - yellow for any at all and reddish when 10 or greater. Rather than the instantaneous count, SES displays the total for the past 5 minutes instead to maintain visibility.
The SES count also appears on the dedicated All User Stats page, again totaled over for 5 minutes. It can't be ordered by that column though as the data isn't in the same format but ordering by Errored Seconds will
usually also show SES at the top.
I believe I'm correct in saying that ONE Errored Second results from at least ONE code violation (CRC for example) within any second OR at least one Loss of Service event occurred - and that ONE Severely Errored Second has at least TEN code violations in any second. So lots of ES does not necessarily mean a corresponding increase in SES. And that the DLM system possibly takes more immediate notice of continuing high SES counts.
Also, thanks to all those who donated in the past month to help keep the system running