Not a top priority one, but in our old Monitoring platform we had a really good and customisable Ops UI. This consisted of a line per-check but then we could customise how many hours we were seeing for each check, and horizontally the bar which showed performance & state ran almost the entire length of the screen.
For an average check which runs every 10 minutes this equates to 144 runs per day, and that UI had the granularity to show each run visually from one central screen. The net effect was if you had one check run as a fail, it was clearly visible that that was less than 0.7% of the daily results - you saw a slice of red rather than a chunk!
I mention this because the design choice in Apica is that in the dash or ops views you see 24 hours of data represented in 24 segments. A single check run that fails looks like anywhere between 1 - 6 check runs failed. Personally what I have noticed is it worries non-technical people a whole lot more than the old system! Worried staff have less buy-in and trust the system less.
a) You could add another timeline Ops view which more closely mirrors the above. It's actually a really powerful view and to be honest it was better for us, especially because it gave that granularity.
b) Some customisation so that the regular dash view makes better use of the horizontal space. If you load our dash on an average TV screen (1920px wide) you will see a whole ton of wasted space between the name of the check and the start of the last run section. You could literally double the size of the 'Last 24hr' bar and not make things too crowded.
I know one size rarely fits all but hopefully the feedback on how people perceive the monitoring through the UI choices vs the old system is useful and some features can be added in the future to make things better.
This has unfortunately been pushed until furhter notice.