Optimize Event and Notification Lists

[flourish86]

** Work in Progress **

Users

• experienced Icinga (Web) users
• unexperienced Icinga (Web) users, that use Icinga Web only for gathering quick information

Context of Use

• Quickly identify problem sources after an outage
• Users need to quickly recognize, when events occurred and if users have been notified
• they need an overview in context of other events (list)

Problems

• Relative Time Stamps make it hard to identify, when older events occurred in context of other events
• relative time stamps are helpful, tough, for more recent events
• the dense information makes it hard to extract critical information

Preferred Solutions

Event List

Group Event by day

• Add a separator per day to the list
  -- A the visual break helps to get a better overview of, on which day the events occurred and avoids redundant information.
  -- As the timestamps are on the right hand side of the list item, aligning the date to the right makes it easy to scan by time, while focussing on scanning for visuals on the left side
  --

Display absolute timestamps

• Use absolute timestamps by default
  -- While using absolute timestamps should be used by default since they allow for more precise contextual analysis, relative timestamps can be more helpful for analyzing only recent events (especially when the view is used as a dashlet)
  -- Add an option for relative timestamps
  

Add notification information

The suggestions are probably technically not feasible, so here are some variants.

Expand with notification preview

Display notification count

Display icon, if any notifications have been sent.

Declutter the event list

• Remove unnecessary information
  ** Current object states
  ** last Hard state

++++ to be continued ++++