Hi Ryan,

In short, the root time is the time the alarm originally started and this will never change. The other time is the time when the change happened to the alarm.

Basically, an alarm starts at a certain point in time, that is the root time. The time it was first detected. Then an alarm record is created of the type 'new alarm' with both the time and the root time set to that time (see also below screenshot).

Then things can happen to the alarm, e.g. severity can escalate, a user can take ownership, etc. Each time something happens with the alarm, it needs to be updated and a new record is created in the life cycle of that alarm. Then you have a small arrow in front of the alarm to open the history of that alarm.

In the below example the alarm escalated to a minor alarm, in that record the root time remains on the original time, this time never changes, but the time field indicates when the alarm escalated to a minor alarm.

In other words, the root time is the original start time of the alarm, the time is the time of the last change (or the change of that record because you can have a life-cycle with a whole series of records in there, a long history of an alarm).

Let me know if something is not clear.

Bert

Hi Ryan,

As far as I know, alarms are not reset to the current time. However, you might be observing alarms being recreated following a DMA or element restart.

For instance, if you're monitoring a specific row in a table and the element removes and then re-adds that row after an element restart, this can trigger a new alarm.

There could be other use cases where this behavior is intended, but these are for specific corner cases.

Hope it helps.