

What happened in the cluster, newest first.
Events have hashed names, so the list has no Name column, and opening one shows its reason and object as its title. Events aren’t changed by hand: they have no actions, and their rows can’t be selected.
Only the warnings
The chips above the list count each type. Pick Warning to hide the routine events. The overview’s Warnings tile opens the list this way. The filter (/) matches an event’s reason, message and object name as well as its labels, so typingOOMKilled or a pod’s name finds what you’re after.
On a timeline
List | Timeline, in the list’s bar, shows the same events where they fell in time. The timeline has a row for each object, with its kind and name; click the name to open the object. A Normal event is a hollow circle and a Warning a triangle. One that repeated is a bar from its first time to its last, with how many times beside it where there’s room, and always in its card. Marks too close to tell apart are drawn as one, with how many, and so are repeated events too many to stack in a row; click one to zoom in and part them. A key under it says what each mark means.

Events on a timeline: each a bar from when it began to when it was last seen.
?as=timeline), so a link opens the timeline too. On a phone, or where the page is too narrow for it (beside an open object, say), events stay a list.
Notifications of new warnings
Lumovi can tell you of new Warning events in a cluster as they happen, through your system’s notifications. It’s off until you turn it on, for each cluster:

Notifications of new warnings, in a cluster’s settings.
- On the desktop, in the cluster’s settings: Notify me of new warnings. While Lumovi is open, whatever page it shows, it checks every 30 seconds.
- On a server, in the cluster switcher at the top of the sidebar: Notify me of new warnings. It’s yours alone, kept in this browser, and works while one of Lumovi’s tabs is open in it, hidden or not. Your browser asks first: Allow notifications, then Send a test to see one. A browser that blocks them says so, and the switch stays on until you allow them in its settings for the site; one that can’t show notifications at all says “This browser can’t show notifications.” With several tabs open over HTTPS, one of them checks, and you’re told once.
An object’s own events
Every object’s detail panel has an Events tab with the events about it, newest first. It’s often the fastest way to see why a pod won’t start or a volume won’t bind. The overview lists the latest warnings across the namespace, too. When an object has more than 200 events, Filter events appears above the list. It finds events by their reason, their message or what reported them, and says how many match, like 12 of 3,000. Your browser’s own find reaches only the events on screen then, since a long list is drawn as you scroll. Where the panel is wide enough, the tab has List | Timeline too: its timeline has a row for each reason, likeBackOff or Pulled, and works as the page’s does. Lumovi keeps your choice for every object’s tab.
Kubernetes keeps events for a limited time (an hour, unless the cluster is set up otherwise), so old ones disappear. The timeline says so under it: All is only what’s still kept. For a longer view of what a workload did, see Usage history and its logs.
Overview
The latest warnings, next to what needs attention.
Health and status
What the statuses on each object mean.