Live imports · plotsrv demo

Stream controls

Run

Plot controls

Plot type Category i Aggregate i

Palette

Order i Categories i

Advanced

Custom title Title alignment X-axis label Y-axis label X scale Y scale Include zero baseline When over point limit

Plots use only loaded rows that pass the current browser filters.

Waiting for appended JSON objects.

Since last visit

About Since last visit

Compares the stream’s current cumulative counters with a compatible checkpoint saved by this browser for this view. It reports changes in accepted records, source severities and noteworthy observations, not a replay of every log entry.

The comparison baseline stays fixed during this visit while newer checkpoints are saved in local storage. Refreshing or returning can start a new comparison from the most recently saved checkpoint—not necessarily the moment you closed the page.

A first visit, cleared or unavailable browser storage, a new session, or incompatible stream state can prevent comparison. Continuity warnings mean the source may have gaps. Table filters do not change these counters.

A simple comparison with this browser’s previous compatible visit.

Waiting for current stream state.

Noteworthy

About Noteworthy

A bounded, server-selected list for this stream session—not anomaly detection, a significance test, or a complete log. One source record can qualify more than once.

Source severity. Checks top-level severity, then level, taking the first recognised value. Accepted values are warning (warn also matches), error, critical, fatal, alert and emergency. Matching ignores letter case, but not whitespace. Nested fields and words in message text do not count. A warning is the producer’s label, not plotsrv deciding the reading is rare.

First appearances. Retains a new string, boolean or null value in level, severity, status, state, kind, event, type. Numeric values do not qualify here. Tracking is bounded per field (defaults: 16 distinct values and 128 UTF-8 bytes per JSON-encoded value); further or oversized values are not tracked.

New numeric lows/highs. Only finite JSON numbers in duration, duration_ms, elapsed_ms, latency, latency_ms, size_bytes, payload_bytes, request_bytes, response_bytes, count, rate, temperature qualify. The first value establishes the baseline; only a strictly lower or higher later value creates an item. Numeric strings and booleans do not qualify. Arbitrary fields such as value are not automatically checked for outliers.

System notices. Separate plotsrv observations describe source continuity changes or uncertainty, reported rejected records, rejection-counter resets and schema changes. They are not original log rows.

Retention and flaws. The default cap is 64 items (configurable). When full, ordinary first-appearance/extrema items are removed before system notices, then source-severity items; the oldest item within a priority is removed first. All recognised severities have equal priority: frequent warnings can displace older errors. This is not a frequency-ranked or complete incident list.

Refresh and tips. Refreshing the page, table filters and pausing the browser display do not reset server classification. A new stream session starts fresh tracking. Server restarts and historical availability depend on storage and retention; without storage this is not a durable archive. Times show when plotsrv observed an item, not necessarily the producer’s event time. Time-ago labels update when the list renders.

Use source severity deliberately and set meaningful thresholds in your producer. For example, a one-SD threshold flags about 42% of a uniform distribution’s readings, so it is not a rare-event threshold. Inspect Technical details for the original record and why it was retained; use the source log for a complete audit.

A bounded recent selection of deterministic observations, not a complete event history.

Loading noteworthy activity…

Featured

Stream controls

Plot controls

Supporting table

Settings

Appearance

Live updates

View navigation

About this dashboard