We are seeing inconsistent alarm formatting when opening multiple DataMiner Cube sessions using the same user on the same DataMiner System.
When we open cube, the alarms from the start are shown as read and are displayed normally. However, when opening another Cube session with the same user, some of those same alarms are displayed in bold, while others appear greyed out/italic.
Below is a screenshot showing the two Alarm Consoles side by side for the same user.
What could cause the same alarm records to be displayed differently between Cube sessions for the same user? Is the read/unread state not expected to be synchronized and persisted across Cube sessions?
Hi Daniela,
The read/unread status is maintained independently in each running Cube session, even when both sessions use the same Dataminer account. Marking an alarm as read in one Cube does not automatically mark it as read in the other, so the same alarm can appear bold in one session and non-bold in another.
Cube does save its read-alarm list locally when disconnecting and can restore it in a later session, but this is not live synchronization between sessions.