| eG Monitoring |
|---|
|
The SuperManager Alarm Window When you login to the SuperManager as egsm, you will be welcomed by the CURRENT ALARMS window. The default user to the eG SuperManager is egsm with password egsm. This user has unrestricted rights to the SuperManager, and can view alarms/status information pertaining to all the individual managers that are being managed by the eG SuperManager. The SuperManager's CURRENT ALARMS window displays the consolidated list of issues encountered by each of the eG managers that have been configured to report to the SuperManager. The alarm details include the component type that has suffered a performance degradation, the component name, a brief description of the issue, the problem layer, the problem date and time, and the manager that reported the issue. To perform further diagnosis, click on an alarm in this page. This will lead you to the corresponding manager's monitor console where the problem layer, test, and measurements are displayed. Besides the default user egsm, the eG SuperManager supports all other Monitor, Supermonitor, Alarmviewer and SuperAlarmViewer users registered with each of the individual managers reporting to it. The access rights defined for them in their respective managers will automatically apply. Accordingly, the alarms displayed in this page are specific to the services and servers being monitored by the current user. Also, if a particular user has been configured to view only a specific priority of alarms then this window will display alarms pertaining to that priority only. However, users with Admin or ServerAdmin privileges cannot login to a SuperManager, as the SuperManager does not support an administrative interface. A central administrative console that will allow one-time configuration of components/tests/user-roles/users has been planned for the future versions of the eG SuperManager. Until then, all admin-related activities need to be carried out from the respective managers. The eG SuperManager has hence been built on the premise that no inconsistencies/duplications exist in user/user-role definitions across managers. The alarms are categorized into Critical, Major, and Minor priority alarms. According to the color-coding, red indicates Critical alarms, orange indicates Major, and pink denotes that the alarms have Minor priority. The alarms are arranged in the descending order of their priority. By default, pointing the mouse over an alarm reveals additional alarm information in the form of a brief description of the problem, the test that detected the problem, the host on which the test executed, and the corresponding service name (if any). Accordingly, the MOUSE_OVER parameter in the [ALARMS] section of the eg_supermanager.ini file (in the {EG_INSTALL_DIR}\manager\config directory) is set to true by default. By changing the MOUSE_OVER flag setting to false, you can make sure that the additional alarm information always appears in the CURRENT ALARMS window, regardless of whether or not the user moves the mouse pointer over an alarm. Moreover, if the MailLastValue in the eg_services.ini file (in the {EG_INSTALL_DIR}\manager\config directory) is set to yes, the last measure value and unit will also appear along with the additional alarm details. Also, for an AlarmViewer / SuperAlarmViewer, these alarm details will be accompanied by a FEEDBACK icon and a HISTORY icon. To record feedback on when and how the problem represented by the alarm was fixed, click on the alarm and then, click on the FEEDBACK icon. To view the past history of fixes for a problem, click on the alarm and then click on the HISTORY icon. Additionally, at the right top corner of the window, a Show list box exists. Users can selectively view the alarms in the alarm window, by choosing an alarm priority from this list box. To view all the alarms, select the All option from this list box. To view only the Critical alarms, choose the Critical option, and to view the Critical and Major alarms, pick the Critical & Major option. Similarly, pick the Major to view only the Major alarms, and the Minor option for Minor alarms. This window can also be opened using the Alarms option in the SuperManager main menu. The option to DELETE ALARMS can be enabled for specific users registered with the eG system. This can be performed by providing a specific monitor user's login name against the ALLOW_DELETE parameter in the [ALARMS] section of the eg_supermanager.ini file (in the {EG_INSTALL_DIR}\manager\config directory). By default, the ALLOW_DELETE parameter will hold no value, indicating that the DELETE ALARMS option will not be available to any user by default. [ALARMS] ALLOW_DELETE=john In the above example, note that the ALLOW_DELETE parameter contains the value 'john'. This ensures that when the user 'john' logs into the eG SuperManager interface, the ALARMS window displays an additional DELETE ALARMS button. To delete an alarm, select the check box corresponding to it and then click the DELETE ALARMS button. Note: By default, the CURRENT ALARMS window refreshes every 90 seconds. This is indicated by the AlarmsTime setting in the [REFRESH] section of the eg_supermanager.ini file (in the {EG_INSTALL_DIR}\manager\config directory), which is set to 90 by default. If need be, you can change this refresh period by editing the AlarmsTime setting in the eg_supermanager.ini file. Similarly, you can also override the default refresh frequency for user sessions. To achieve this, simply modify the default value of the UserObjectRefreshTime parameter (which is, 180 seconds) present in the [REFRESH] section of the eg_supermanager.ini file (in the {EG_INSTALL_DIR}\manager\config directory). Likewise, you can also modify the default timeout period for user sessions from 600 seconds to a value of your choice. Time out period refers to the duration beyond which the eG system will automatically terminate idle user sessions. To make changes to the default timeout period, open the eg_supermanager.ini file (in the {EG_INSTALL_DIR}\manager\config directory), and alter the value displayed against the UserObjectIdleTime parameter in the [REFRESH] section of the file. |