Events and Incident History Improvements

[nilmerg]

Recent changes to icinga-notifications made internal events appear in the events listing. They are currently shown like this:

Events

Prerequisites

It is currently not possible to differentiate between internal events. The daemon needs to write them to the database in a way, this can happen: Icinga/icinga-notifications#162

Until the daemon is updated, the differentiation could temporarily happen based on the message.

Missing Visual

There should be an icon visible. The icon must be the same that's used by the Incident History. Scroll down for details

Incorrect Title

acknowledged is only the default phrase. For each type of event a new phrase should be added. At the moment, the phrase is identified based on the event severity. Since the severity was previously only missing for Acknowledge events sent by Icinga, the same phrase is used for internal events as well.

Incorrect Source Icon

Internal events have no source, the icon is only shown because they are tied to objects still and such have a source. The source icon must reflect that they are internal events emitted by icinga-notifications. There's no icon or logo for this yet. @flourish86 may have input on this.

Event Detail

Incorrect Header

Once the visualization in the events listing is changed, this should be automatically reflected here.

Missing Incident

This is an issue in icinga-notifications, as there's no entry in the incident_event table for internal events: Icinga/icinga-notifications#151

Source

This is again the source of the related object. The icon used should be the same as in the events listing for internal events and the label should just be Icinga Notifications.

Incident History

Object Name

The name of the object is redundant and doesn't need to be repeated on every severity change. Must be removed.

Visuals

Should use the new icons mentioned below.

Content

At the moment, source events are not shown. Only incident events. This should be extended so that source events are also visible, so that if a source event is listed, the incident events caused by it appear chronologically afterwards. (Yes, this means that the first severity!=ok event is the first, and incident opened the second.)

The list can grow very large, if an incident is open for a long time. We should limit the history shown in the detail to a definite number of rows. (e.g. 15) All history entries should only be listed in a separate tab which works the same as host/service history tabs in Icinga DB Web.

[flourish86]

I listed the icons for the internal events here.

Also the internal events' appearance should be different from the status changes. In this example I made the external events' icons a little bigger. Please also note that the status icon shapes are contained in the FontAwesome icon glyphs, while the internal event visuals have a circular element applied on them.

Let me know, if you need css details for the updated styles.

[flourish86]

The message phrases are also not very user-friendly and could be improved visually and writing-wise.

Here are some suggestions, that could be discussed.

more to come …

[nilmerg]

Linking the recipient is currently questionable. We have no dedicated detail view, only a configuration form in case of contacts, and that is out of scope for this issue.

[ncosta-ic]

Incorrect Source Icon

Internal events have no source, the icon is only shown because they are tied to objects still and such have a source. The source icon must reflect that they are internal events emitted by icinga-notifications. There's no icon or logo for this yet. @flourish86 may have input on this.

I currently render internal entries on the event list like the following:

@flourish86 Did you already come up with a design idea, on how we should differentiate events that are tied to a source (showing the source icon next to the "0m 00s ago") and ones that are not tied to a source (like in my example above where I placed a text placeholder)?

[ncosta-ic]

Incorrect Source Icon

Internal events have no source, the icon is only shown because they are tied to objects still and such have a source. The source icon must reflect that they are internal events emitted by icinga-notifications. There's no icon or logo for this yet. @flourish86 may have input on this.

@flourish86 Did you already come up with a design idea, on how we should differentiate events that are tied to a source (showing the source icon next to the "0m 00s ago") and ones that are not tied to a source (like in my example above where I placed a text placeholder)?

It was decided to drop the source information on internal events altogether, since they don't originate from an actual data source.