Job Management Partner 1/Software Distribution Administrator's Guide Volume 1
The following five methods are available for reporting alerts:
Which methods to use should be determined based on the client's operating environment. For example, if the client user wants to be immediately notified of any alert, you can use pop-up messages. If the client PC is unattended, you can specify that alerts be reported to a higher system only.
This section explains how to specify alert reporting methods and how to check alerts. For details about how to set up the Conditions Settings for System Monitoring window, see 11.8.2 Specifying system monitoring conditions.
To display the current usage status of hard disks and memory on the System Conditions page of Local System Viewer:
An item for which Monitoring is specified is displayed in black letters on the System Conditions page and its status is automatically updated every 30 minutes. If Hard disk space usage or Virtual memory usage exceeds a preset threshold, a warning symbol () or a symbol indicating a critical state (
) is displayed to the left of the item name. The following figure shows a display example of the System Conditions page.
Figure 11-29 System Conditions page (displaying a symbol indicating critical state)
In this example, hard disk space usage has reached 85%, exceeding the critical threshold (80%), and a symbol indicating a critical state () is displayed. The threshold displayed was specified in the Conditions Settings for System Monitoring window.
The display is updated at a different timing for each monitoring item depending on the setting in the Conditions Settings for System Monitoring window. When Monitoring is disabled for a monitoring item in the Conditions Settings for System Monitoring window, the monitoring status on the System Conditions page is not refreshed. Items with statuses that are not refreshed automatically are displayed as gray text.
To immediately refresh the display of the System Conditions page, choose View and then Refresh. Doing so refreshes the status of all items, including those for which Monitoring is disabled.
The following table shows the relationship between the Monitoring option settings in the Conditions Settings for System Monitoring window and display refreshing on the System Conditions page.
Table 11-3 Display refreshing on the System Conditions page
Monitoring item setting | Can the display be refreshed? | |
---|---|---|
Automatic refresh every 30 minutes | Refresh menu | |
Monitoring enabled | Y | Y |
Monitoring disabled# | N | Y |
#: Displayed as gray text on the System Conditions page.
If the client's system monitoring is stopped, monitoring items are not displayed on the System Conditions page. Only a message indicating that information cannot be collected is displayed.
To display alert message history on the Alert History page of Local System Viewer:
When these settings are specified for an item, system monitoring acquires history items for alerts that are reported. You can use the Alert History page of Local System Viewer to check the acquired history. The following figure shows the Alert History page.
Figure 11-30 Alert History page of the Local System Viewer window
The Alert History page displays the following items:
You can output the content of the Alert History page to a CSV file. For details about the operations on this page, see 11.7.3 Checking the list of alerts reported.
You can report an alert by displaying a pop-up message when system monitoring detects an error. The user can immediately recognize the risk and check the alert message.
To report an alert by displaying a pop-up message:
When the hard disk or memory usage exceeds the threshold, the Alert Report dialog box is displayed. The following figure shows this dialog box.
Figure 11-31 Alert Report dialog box
When the client is connected to a higher system, it can report alerts to the higher system. When an unmanned client PC is remotely controlled, reporting alerts to the higher system only without displaying pop-up messages or acquiring alerts history is more convenient.
To report an alert to a higher system:
At the higher system, it is possible to check the alert messages sent from all clients, by means of a CSV file, Windows NT Event Viewer, or JP1/IM - View's Event Console window. This enables the system administrator to be kept informed of the alert status at all clients. The higher system can also report alerts to the system above it. For details about how to check alert reports at a higher system, see 7.4 Checking alert information reported from clients.
For the higher system versions that can check or relay reported alerts, see 7.4.2 Relaying alert information.
You can report alerts based on changes in the appearance of the System Monitoring icon when system monitoring detects an error. The user can instantly recognize the risk even if no pop-up message is displayed.
To report alerts based on changes in the System Monitoring icon:
When an alert occurs for the item for which handling is specified, the System Monitoring icon changes its appearance to an alert-reporting state as shown in the following figure.
Figure 11-32 System Monitoring icon (in the alert-reporting state)
By double-clicking the System Monitoring icon and displaying Local System Viewer, you can check the item for which the alert occurred and its state. For details, see (1) Displaying usage status on the System Conditions page of Local System Viewer.
After the System Monitoring icon goes into an alert-reporting state, it returns to its original state () once the monitored state returns to normal. If multiple alerts have been reported, the System Monitoring icon stays in the alert-reporting state until all of the monitoring items return to normal.
All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.