It's a plain, invented log viewer on my own test machine. The screenshot shows total CPU time accumulated since the program started. Somebody read eleven hours as "it is consuming eleven hours right now". CPU rates for intervals, per-process elapsed time, cumulative CPU time: I wanted to put the three on one page before the debate spreads to the microwave.
Someone sent me a screenshot with eleven CPU hours and the word MALWARE in little red letters
Incident responseObservabilitySecurity operationsThat's the bit I wanted. I'd love that in the first message I get on shift: last normal time, when people started feeling it, what you could still use. I don't mind you not knowing the cause. I mind the bloody graph becoming the entire incident two handovers later because nobody wrote down that the people at the front desk couldn't type. Last time I walked out to the desk, their browser already had the last ticket in it and the queue was gone. I could cheerfully have announced that the service was back. The woman there asked if I'd like to try printing my ticket. I still have the little white slip it spat out. Nothing on it for the passenger except the date.
Cheers @SameWhen_. Hanging on to that first sentence for next time. My own screenshot didn't include any of the people yelling behind me.