I can get a better clue. I can sort by count. I can start getting a feel for what’s going on here. But it’s really hard to explain to management or to see problems in this. So there’s a chart called the time table which is a very visual view of this which people can use to start seeing the story. It’s the same data as on the first page, but it’s grouped into 30 categories.
Across the horizontal axis we’re looking at transactions at the second level across the day. So for example these collect firmware revisions. Each of these texts is in an event. They have it early in the day. Then there’s none in the rest of the day. Execute commands happen pretty regularly through the day, and here it’s a little hard to see, but there are long tails here which means they last a long time.
This chart on the right is totaling the events across the dates for each of these command groups, and it dominates. You see this other unusual pattern like this user prompt is not doing anything. It comes on with some long interval and goes silent and comes back again. So somebody who knows manufacturing data can look at this and see that there are some unusual patterns.
We’ve, in fact, coded them by fault levels: Major Fault A, Major Fault B and no fault. Let me just do some visual discovery. I select a two fault types. The chart on the left colors only those fault types. Now so I see major Fault A occurs only in the user prompt and for this duration here. This might be hard to see in the webinar, but there’s a couple of shorts spikes out here for the same user fault.
The blue one Major Fault B happens only in executive commands, and it happens in the late morning and then again in the afternoon as gaps appeared when everything else has gone silent. I might say I want to just drill on the user prompt. Let me grab that one. I’d go back to the first page and my detailed view has changed to show my 32 event logs that were in that fault category.