History of Acknowledgements

In large environments, it is but natural that the same set of components are assigned to multiple users for monitoring. In such environments, some/all the users with monitoring rights to a component might want to post their comments for an alarm related to that component. If acknowledgment rights are granted to all these users, then each of them can login to the monitor interface and provide an acknowledgement description for the same alarm. eG Enterprise maintains a history of the acknowledgement descriptions provided by multiple users with rights to monitor a single component, and presents this information to these users via the eG monitoring console. This way, the administrative staff can share the responsibility for resolving critical issues, brainstorm online to identify accurate remedies, and even provide each other with quick updates on problem status.

To enable users to quickly access this historical acknowledgement information, the eG monitoring console embeds multiple mechanisms. While the History of Alarms page and the Current Alarms window display all the acknowledgement descriptions associated with a particular alarm, to enable users to selectively review specific acknowledgement descriptions, the eG monitoring console provides the specialized History of Acknowlements page. This page provides a wide variety of filter options with the help of which users can quickly and easily run a search across all alarm acknowledgements, and swiftly locate the acknowledgment information of interest to them.

To access this page, you have to select the History of Acknowlements option from the Alarms tile:

• When this page appears, do the following to access the acknowledge details you want:
  • To view all alarm acknowledgements related to a particular component type, pick a Type from the list box.
  • To view all the acknowledgements associated with a particular component, select an option from the Component list.
  • If you want to view all the acknowledgements submitted by a particular user, then pick an option from the User list.
• To override the default settings of the History of Acknowlements page, click on the icon. The Settings pop-up window appears:
  • By default, the History of Acknowlements page provides the details of all the acknowledgements that were submitted during the last 24 hours. Accordingly, the Timeline is set to 24 hours by default. If need be, you can change this Timeline, so that the page displays only those acknowledgements that were submitted during the specified timeline.
  • By default, the History of Acknowlements page displays all acknowledgements that were submitted for all types of alarms, regardless of the problem status. Accordingly, the Alarm Type is set to All by default. However, if you want to view only those acknowledgements that pertain to the open alarms, pick the Open option from the Alarm Type list. Similarly, you can pick the Closed option from this list to view the acknowledgement information that related to closed issues only.
  • You can even indicate how many acknowledgement records need to be provided per page by picking an option from the Records per page list.
  • Finally, click on the Show Details button.

• The resulting report then provides the acknowledgement history that fulfills the specified conditions.
• While you can save the report as a CSV file by clicking on the CSV icon in this page, you can save the same as a PDF document by clicking on the PDF icon.

History of Deletions

Typically, in large, multi-user environments, multiple users may be granted the privilege to monitor a single component. In such environments, any of these users can delete an alarm raised on that component without the knowledge of the others, thereby causing confusion. To avoid this confusion, eG Enterprise provides users with the ability to track the deleted alarms.

While the History of Alarms page displays the deletion details of every alarm that was deleted in the recent/distant past, it does not allow you to search/filter based on the displayed alarm deletion information. Sometimes, you might want to view the details of all alarms that were deleted by a particular user. Similarly, you might want to view only the details of those alarms that were deleted during the last 24 hours. This deletion-specific filtering cannot be performed using the History of Alarms page. The eG monitoring console hence provides a dedicated History of Deletions page. This page provides a variety of filter options using which you can quickly access the alarm deletion details that you want to view. To access the History of Deletions page, select the History of Deletions option from the Alarms tile.

• When this page appears, you can use any of the filter options discussed below to quickly retrieve the deleted alarm information that you are looking for:

  • To view the details of all deleted alarms related to a particular component type, pick a Type from the list box.
  • To view the details of those deleted alarms that pertained to a particular component, select an option from the Component list.
  • If you want to view all the alarms deleted by a particular user, then pick an option from the User list.

• To override the default settings of the History of Deletions page, click on the icon. The Settings pop-up window appears:
  • By default, the History of Deletions page provides the details of all the alarms that were deleted during the last 24 hours. Accordingly, the Timeline is set to 24 hours by default. If need be, you can change this Timeline, so that the page displays the details pertaining to those alarms that were deleted during the specified timeline.
  • You can even indicate how many alarm records need to be provided per page by picking an option from the Records per page list.
  • Finally, click on the Show Details button.

• The resulting report then provides the deletion history that fulfills the specified conditions.
• While you can save the report as a CSV file by clicking on the CSV icon in this page, you can save the same as a PDF document by clicking on the PDF icon.