Monitoring

Monitoring is the dashboard for the whole application: every running instance added up. It polls every five seconds, and the charts hold the last thirty readings, so each of them covers roughly the last two and a half minutes. With nothing running, the live sections are replaced by a note pointing at Instances.

Pipeline

The three stages of generation as one row of totals, each carrying the losses that explain the gap to the next.

Read left to right, the row locates where events are going missing without opening a single instance.

Throughput and failures

The Throughput chart plots input against output as rates measured between polls — the rate now, rather than the average since a generator started that the Instances table reports.

The Failures chart covers the same window, split into the event stage and the output stage. It is present only while something is failing.

Instance load

Each instance's share of the total output rate, stacked over the same window. An instance that dominates the pipeline, or has quietly stopped contributing to it, shows up here.

Resources

CPU and memory for the host, disk and network for the Eventum process, each with its recent history.

Read next to the throughput chart, these separate a slow generator from a saturated machine: output that plateaus against a CPU ceiling is a different problem from output that plateaus with the machine idle.