12.1.5 Monitoring by using the Integrated Operation Viewer
You can perform the following operations by using the Integrated Operation Viewer of JP1/IM2 through linkage with JP1/IM2 version 12-10 or later.
- Organization of this subsection
(1) Displaying the operating status by using the PFM - Web Console window
(a) Overview
By displaying the PFM - Web Console window on the Performance tab in the Details area of the Integrated Operation Viewer window of JP1/IM2, you can view the operating status of the Performance Management's monitoring agent without the need to log in to PFM - Web Console (that is, with just a single sign-on). Note that this monitoring agent is the one you have selected from the components (IM management nodes) in the Operating status area. This operation is available when the version of PFM - Web Console is 12-10 or later.
Even when JP1/IM2 manages multiple PFM - Managers, the PFM - Web Console at the connection destination is automatically detected and displayed. Almost all functions you can access from the PFM - Web Console window of Performance Management are available, including displaying of reports, setting of alarm table binding, and changing of log collection conditions.
In addition, when PFM - Web Console is version 12-50 or later, you can view Performance Management reports in the PFM - Web Console window by using monitor startup from a Performance Management event shown in the Events area or using the JP1/IM2 suggestion function in the Integrated Operation Viewer window of JP1/IM2.
For details on the PFM - Web Console window that is displayed by the Integrated Operation Viewer, see the chapter describing the PFM - Web Console window displayed by the Integrated Operation Viewer of JP1/IM2 in the manual JP1/Performance Management Reference.
(b) JP1 user permissions
Only JP1 users with Performance Management permissions described in the following table can display the PFM - Web Console window by using the Integrated Operation Viewer.
|
Performance Management permission |
JP1 permission level |
|---|---|
|
Management user |
JP1_PFM_Admn |
|
Ordinary user |
JP1_PFM_Operator |
(c) Number of simultaneous connections allowed
A maximum of 64 simultaneous connections# (which includes a connection made to PFM - Web Console to start it from JP1/IM2 and a connection made to PFM - Web Console to independently start it without linkage with JP1/IM2) are allowed to a single PFM - Web Console.
- #
-
This indicates the number of user accounts that can simultaneously log in to one PFM - Web Console. For details, see the section in the appendixes describing the number of user accounts that can simultaneously log in to PFM - Web Console in the JP1/Performance Management Planning and Configuration Guide.
(d) Performance Management components for which to display the PFM - Web Console window
The following table describes the components of Performance Management for which the PFM - Web Console window is displayed through the Integrated Operation Viewer.
|
Components of Performance Management |
Whether to display the PFM - Web Console window |
|
|---|---|---|
|
PFM - Manager |
Yes |
|
|
PFM - Base |
No |
|
|
PFM - Agent (an agent-specific category and an Agent Collector service under the Management Applications category#) |
Yes |
|
|
PFM - RM |
Remote Monitor Collector service |
Yes |
|
Group agent |
Yes |
|
|
Remote agent (an agent-specific category and a remote agent service under the Management Applications category#) |
Yes |
|
|
Other than the above |
No |
|
- Legend:
-
Yes: The PFM - Web Console window is displayed.
No: The PFM - Web Console window is not displayed.
- #
-
One of the categories that summarize the operation management products of JP1
(e) Functions available from the PFM - Web Console window
The following functions are available from the PFM - Web Console window displayed by using the Integrated Operation Viewer.
- - When you select PFM - Manager from the components of Performance Management
-
-
Operation and status display of health check agents (when the health check function is enabled)
- Report display
- Alarm status display
- Alarm binding/unbinding
- Service properties display
-
Summary display of the operating status
-
Temporary disabling of monitoring
-
Event history display
-
Creation, editing, and deletion of alarms/report definitions
-
Display and distribution of service properties
- #
-
Display the Operational Status from the result of the refine search check box is not displayed.
-
- - When you select PFM - Agent or a PFM - RM agent from the components of Performance Management
-
-
Report display for the selected agent#
-
Status display for the selected agent
-
Alarm binding for the selected agent#
-
Properties display for the selected agent
-
Creation, editing, and deletion of alarms/report definitions for the selected agent#
-
Display and distribution of service properties of the selected agent
-
Process monitoring setting for the selected agent (PFM - Agent for Platform or PFM - RM for Platform only)
- #
-
Functions related to reports and alarms are not available for the Remote Monitor Collector service provided by PFM - RM.
-
Note that the following functions are not available from the PFM - Web Console window displayed by the Integrated Operation Viewer:
-
Event Monitor
-
Editing of the Agents tree
-
Checking of alarm application status
-
Bookmarking operation
The following items related to bookmarking are hidden from view and therefore cannot be selected.
-
Bookmarks that show up in the Tree type drop-down list in the following windows:
- The Display Reports > Select Report window displayed from the Agents tree
- The New Report > Drilldown > Select Report window displayed from the Reports tree
- The Edit > Drilldown > Select Report window displayed from the Reports tree
-
The Bookmarks anchor, which is displayed when a tab other than the Edit Report Definition page is selected in the View Report window, and the Baseline anchor, which is displayed when the View report page is selected
-
Bookmarks that show up in the Drilldown report selection list that is displayed when the Edit Report Definition page is selected in the View Report window while setting drilldown reports
-
-
Stopping of services
(f) Login and logout
When you display the PFM - Web Console window by using the Integrated Operation Viewer, you are automatically logged in to or out of PFM - Web Console when you perform one of the operations described below.
After you display the PFM - Web Console window, you remain logged in to it even when you perform another operation in the Integrated Operation Viewer window or are directed to another window, and the PFM - Web Console window becomes hidden from view. In this case, however, the operations you have performed in the PFM - Web Console window are discarded, and the Agents window is displayed.
- - Operations that trigger automatic login
-
-
When you log in to the Integrated Operation Viewer window and then from the Operating status area, select a component of Performance Management for which you want to display PFM - Web Console for the first time (or when you select a component for the first time after the PFM - Web Console session times out)
-
When, at the connection destination, the secondary PFM - Web Console takes over the primary PFM - Web Console, or vice versa, in an environment where a multiple-monitoring configuration is used
-
When you click the Log in again button
-
- - Operations that trigger automatic logout
-
-
When you log out of the Integrated Operation Viewer window
-
When the JP1/IM2 session times out#1
-
When you close the Web browser (when you click the x button of the Web browser)
-
When, at the connection destination, the secondary PFM - Web Console takes over the primary PFM - Web Console, or vice versa, in an environment where a multiple-monitoring configuration is used
-
When the PFM - Web Console session has timed out#2 without any user operations or automatic updating performed on PFM - Web Console
-
When you click the Log in again button
- #1
-
You can adjust the JP1/IM2 session timeout setting by editing the value of COM_SO_TIMEOUT in the communication environment definition file (console.conf.update) in JP1/IM2. For details, see the JP1/IM2 manual.
- #2
-
You can adjust the PFM - Web Console session timeout setting by editing the sessionTimeout parameter in the initialization file (config.xml).
- Important
-
If you log out of PFM - Web Console via the Integrated Operation Viewer of JP1/IM2, a small browser window with the message Now logged out shows up. This means that logout processing is in progress. Do not close the browser window by clicking the x button on the browser.
If, for example, you stop the PFM - Web Console service and then log out of it, the browser window without the message Now logged out might remain displayed. In this case, close the browser window.
-
(g) Displaying items appropriate to the selected component in tree view
When the Performance tab in the Details area of the Integrated Operation Viewer window of JP1/IM2 displays the Reports window, Alarms window, or Services window of PFM - Web Console, the Navigation frame displays a tree view of the items corresponding to the component of Performance Management that has been selected in the Operating status area.
For details on the items displayed in tree view in the Navigation frame, see the chapter that describes the items displayed in the Navigation frame in the manual JP1/Performance Management Reference.
(h) Operations allowed when the business group function is enabled
-
Agents that the user is allowed to view or operate
-
Agents that are monitoring the hosts that belong to the business group assigned to the user
-
-
Agents that the user is not allowed to view or operate
-
Agents that are monitoring the hosts that belong to the business group which the user cannot reference
-
Agents that are monitoring the hosts to which no business group is assigned#
- #
-
When no business group is assigned to the hosts, business group ordinary users cannot display the PFM - Web Console window. (If they attempt to do so, an error occurs.)
-
-
Agents for which summary display, temporary disabling of monitoring, and event history display can be performed
These operations can be performed for all agents that the business group assigned to the user is allowed to reference.
-
Users who are allowed to use those functions that only PFM - Manager is allowed to operate
Only users who can reference PFM - Manager are allowed to use those functions.
- Important
-
When the business group function is enabled, a business group must be assigned to both PFM - Manager hosts and PFM - Agent hosts.
(i) Operations performed in a multiple-monitoring configuration
In a multiple-monitoring configuration, when you select PFM - Manager in the Operating status area of the Integrated Operation Viewer window, a connection is automatically established to the primary PFM - Manager host at the connection destination. (This operation assumes that the primary PFM - Manager host has been selected in the connection menu display area). From the connection menu display area, you can switch to another connection destination (primary or secondary).
When connection destination switchover from primary to secondary, or vice versa, takes place during system operation, an icon shows up in the connection menu display area to indicate that the switchover has occurred.
(2) Displaying related nodes
You can visualize and display related nodes on the Related node tab in the Details area of the Integrated Operation Viewer window. The related nodes, which are connected to one another with relation lines, refer to those nodes related to the IM management nodes (monitoring agents) of the Performance Management of interest, and they indicate the types of relationships between nodes. Nodes are connected to one another with relation lines. The properties of the selected node or relation line are displayed in Properties.
The following table describes the relationship between Performance Management's IM management nodes for which related nodes can be displayed.
|
Relationship type |
Parent node |
Child node |
|---|---|---|
|
managerAgent |
IM management node corresponding to PFM - Manager |
IM management node corresponding to a service of the PFM - Agent instance managed by the parent node |
|
IM management node corresponding to a service of the PFM - RM instance managed by the parent node |
||
|
IM management node corresponding to a service of a PFM - RM instance |
IM management node corresponding to a service of the remote agent managed by the parent node |
|
|
sameNode |
IM management node corresponding to a service of a PFM - Agent instance |
IM management node corresponding to the performance data of the parent node |
|
IM management node corresponding to a service of a PFM - RM instance |
IM management node corresponding to the group agent of the parent node |
|
|
IM management node corresponding to a service of a remote agent |
IM management node corresponding to the performance data of the parent node |
|
|
primarySecondary |
IM management node corresponding to the primary PFM - Manager (applicable when a multiple-monitoring configuration is used) |
IM management node corresponding to the secondary PFM - Manager of the parent node (applicable when a multiple-monitoring configuration is used) |
- Important
-
-
When a switchover from the primary to secondary Manager, or vice versa, is performed in a multiple-monitoring configuration, use the functionality provided by JP1/IM2 to synchronize configuration information between the two Managers. Until configuration information is synchronized between the Managers, the Integrated Operation Viewer of JP1/IM2 displays the actual parent node as a child node and the actual child node as a parent node.
-
When an attempt to perform a synchronization to reflect the latest configuration information in the primary Manager fails, the Related node tab does not display the relationship between the primary and secondary Managers.
If the relationship between the primary and secondary Managers is not displayed even when the primary Manager is up and running, check the information specified in the target host definition file for configuration collection (imdd_target_host.conf) of JP1/IM2. If you find that neither the primary host name nor the secondary host name is specified in the file, specify them and then try synchronizing them again.
For details on the target host definition file for configuration collection of JP1/IM2, see the JP1/IM2 manual.
-
(3) Displaying trend information
You can display a graphical representation of trend information on the Trends tab in the Details area of the Integrated Operation Viewer window. The trend information is derived from performance data related to the IM management nodes (monitoring agents) of the Performance Management of interest.
The following table describes the information displayed for the Performance Management's IM management nodes for which trend information can be displayed.
|
IM management nodes |
Displayed information |
|---|---|
|
JP1/PFM - Manager under the PFM - Manager host > Management Applications category |
Trend information on health check agents |
|
Agent Collector service under the PFM - Agent host > the PFM - Agent product-specific category |
Trend information on agents |
|
Group agent under the PFM - RM host > Management Applications category |
Trend information on the group agent |
|
Remote agent under the monitored host > PFM - RM product-specific category |
Trend information on the remote agent |
- Adding, editing, or deleting a metric (metric definition file)
The metric definition file is used to define metrics (types of performance data for which to display time-series data) for the trend information that can be displayed for IM management nodes (monitoring agents) of Performance Management. The model file for metric definitions is supplied upon the installation of JP1/IM2. You can add, edit, or delete a metric for which to display trend information by editing the metric definition file. Any changes made to the file are immediately applied when the file is saved.
An attempt to display trend information regarding a monitoring agent fails with the KAJY24106-E message when no metric definition file corresponding to the product ID of that agent exists.
For details on the metric definition file, see the chapter describing the metric definition file in the manual JP1/Performance Management Reference.
- Performance data displayed in a chart
Performance data regarding the Performance Management's IM management node (monitoring agent) from which trend information used to display a chart is derived is stored in the Store database of the monitoring agent. In the case of the PI record type, JP1/PFM plug-in determines the summary block to be used to display performance data by referring to the display period to be displayed in the chart. The range of dates and times you can specify as the display period when displaying performance data in the chart is the same as the range of dates and times you can specify as the report display period (1971/01/01 00:00 to 2035/12/31 23:59) in a report definition.
There are limits to the number of instances that can be displayed in a chart and the number of data items per instance. If the Performance Management's performance data to be displayed in a chart exceeds those limits, adjustments are made so that the data does not exceed the limits and the resulting data is displayed as follows: For details about notification provided in JP1/IM2 windows, see the JP1/IM2 manual.
-
When the Performance Management's performance data has more instances than is allowed, instances are displayed up to the limit.
-
When the Performance Management's performance data has more data items per instance than is allowed, the performance data is summarized. Performance data is summarized according to the summarization rule specified in the metric definition file. For details on the summarization rule, see the chapter describing the metric definition file in the manual JP1/Performance Management Reference.
For details on the maximum number of instances and the maximum number of data items per instance that can be displayed in a chart, see the JP1/IM2 manual.
Notes:
-
In order to display the performance data of Performance Management in a chart, the performance data in question must be stored in the Store database. You must therefore first configure the following settings:
-
Configure the settings necessary to ensure that the records of performance data corresponding to the metrics you want to display in the chart are recorded in the Store database.
-
If the display period to be displayed in the chart includes a period earlier than the default record retention time, make sure to set a sufficiently long record retention time.
-
-
When the Performance Management's performance data is not displayed in the chart, confirm the following:
-
The performance data corresponding to the specified display period exists in the Store database.
-
The performance data matching the filter specified in the metric definition file exists.
-
-
Suppose that the performance data of Performance Management to be displayed in a chart exceeds either the maximum number of instances that can be displayed in a chart or the maximum number of data items per instance. If, under this circumstance, you want to reference raw performance data of Performance Management, display a report from PFM - Web Console of Performance Management.
-
When the instance name to be displayed in a chart exceeds 249 UTF-8 characters, the instance name is truncated at 249 characters. When there are multiple instances having the same name, they are displayed with the item numbers #n (where n denotes a serial number, such as 1, 2, 3, etc.) appended to them as a suffix.
-
The Date and Time field values are used to display a display period in a chart as well as to display a time for each data item to be displayed in a chart. For this reason, under the following circumstances, data might not be displayed even when you specify the display period for which you have acquired performance data, or the time of data might be different from the time at which performance data was acquired:
-
When displaying performance data records of the PI record type
Because records are summarized, the reference time of each summary block becomes the value of the Date and Time field.
-
When displaying performance data of remote agents
The time at which the Remote Monitor Store service recorded the performance data in the Store database, not the time at which the remote agents acquired the performance data, becomes the value of the Date and Time field.
-
- Changing the operation of the JP1/PFM plug-in (JP1/PFM plug-in configuration file)
The JP1/PFM plug-in configuration file is used to define the setting used by the JP1/PFM plug-in to acquire performance data from the Store database. The model file for JP1/PFM plug-in settings is supplied upon the installation of JP1/IM2. By editing the JP1/PFM plug-in configuration file to suit your operation, you can improve the response speed for displaying data in a chart. Any changes made to the file are immediately applied when the file is saved.
For details on the JP1/PFM plug-in configuration file, see the chapter describing the JP1/PFM plug-in configuration file in the manual JP1/Performance Management reference.
(4) Displaying properties
In Propertis on the Related node tab in the Details area of the Integrated Operation Viewer window, you can display properties of IM management nodes (monitoring agents) of the Performance Management of interest.
The following table describes the Performance Management's IM management nodes for which properties can be displayed and provides a description of each property.
|
IM management nodes |
Management Applications category |
PFM - Agent-specific category |
PFM - RM-specific category |
||||||
|---|---|---|---|---|---|---|---|---|---|
|
PFM - Manager |
PFM - Base |
PFM - Agent instance |
PFM - RM instance |
Remote agent |
Group agent |
PFM - Agent instance |
Remote agent |
||
|
Displayed information |
DataModelVersion property |
Data model version of the health check |
-- |
Data model version of each agent product |
|||||
|
ServiceId property#1 |
Service ID of the Agent Collector for health check agents |
-- |
Service ID of the Agent Collector service |
Service ID of the Remote Monitor Collector service |
Service ID of the remote agent |
Service ID of the group agent |
Service ID of the Agent Collector service |
Service ID of the remote agent |
|
|
ProductVersion property#2 |
Product version of PFM - Manager (VV-RR-SS format) Example: 12-50-00 |
-- |
-- |
-- |
-- |
-- |
-- |
-- |
|
|
OsType property#2 |
OS type of the host on which PFM - Manager runs (Windows or Linux) |
-- |
-- |
-- |
-- |
-- |
-- |
-- |
|
|
InstallPath property#2 |
PFM - Manager installation path (with no trailing \ or / added) |
-- |
-- |
-- |
-- |
-- |
-- |
-- |
|
- Legend:
-
--: No property displayed
- #1
-
The displayed service ID is the same as the service ID displayed when the product name display function is disabled.
- #2
-
The prerequisite versions of the products are as follows:
- PFM - Manager 12-50 or later
- PFM - Web Console 12-00 or later
- JP1/IM2 12-50 or later
(5) Displaying suggestion information and taking response actions
(a) Overview
When using the suggestion function of JP1/IM2 of version 12-50 or later, you can display suggestion information (response actions suggested according to the system status of Performance Management) in the Suggestion tab of the Details area and take response actions by selecting an IM management node (monitoring agent) of Performance Management to which a suggestion icon is added in the Operating status area of the Integrated Operation Viewer window.
Performance Management can display suggestion information on the following three use cases and allows you to take response actions.
|
Use case |
Suggestion information definition for use |
Suggestion information to be displayed (JP1/IM2) |
Response action to be taken (user) |
|---|---|---|---|
|
Use case 1 |
Suggestion information 1 |
If there is an event that shows skyrocketing CPU usage (if a warning or error is indicated in the current status of the alarm that monitors the CPU usage bound to PFM - Agent for Platform), the function suggests that you show a Performance Management report to identify the causal process. |
Take necessary action when a report containing the list of processes with high CPU usage is displayed. |
|
Suggestion information 2 |
If an event that showed skyrocketing CPU usage was issued, but the status of the alarm that monitors the CPU usage has currently gone back to normal, the function suggests that you change the response status of the event with the normal status to Processed. |
The response status of the event with the normal status is changed to Processed. |
|
|
Use case 2 |
Suggestion information 3 |
If a Performance Management alarm event or a status change event for an agent was issued, but the status of the alarm or agent has currently gone back to normal, the function suggests that you change the response statuses of all the events with the normal status to Processed at once. |
The response statuses of all the events with the normal status are changed to Processed at once. |
|
Use case 3 |
Suggestion information 4 |
If a large number of events were issued during maintenance of a monitoring host in Performance Management, the function suggests that you suspend monitoring while maintenance is in progress to prevent JP1 events from being issued. |
When monitoring is suspended, perform maintenance tasks. |
|
Suggestion information 5 |
If a monitoring host in Performance Management is in the suspended monitoring status, the function suggests that you resume monitoring after the maintenance tasks are finished. |
Monitoring is resumed. |
(b) Creating and applying a suggestion definition file
You can define suggestion information that is displayed for an IM management node (monitoring agent) of Performance Management by creating a suggestion definition file for each Performance Management use case to be applied. The suggestion definition file must contain suggestion display criteria, suggestion activation criteria, and a response action. A model file (suggestion template) of the suggestion definition file for each use case is provided at the time of JP1/IM2 installation. Furthermore, you can configure the settings shown in 12.1.5(5)(c) Settings for each use case to be applied for each use case you apply.
For details about the suggestion definition file (suggestion template) for each Performance Management use case, see the section describing the suggestion definition file in the manual JP1/Performance Management Reference.
With JP1/IM2 commands, you need to apply the suggestion definition file you created to the JP1/IM2 system. For details about the commands used for applying the suggestion definition file to the JP1/IM2 system, see the manuals or documents on JP1/IM2.
(c) Settings for each use case to be applied
The settings required for each use case to be applied are as follows.
■ Application procedures common to use cases
The suggestion function of Performance Management uses the jp1Imdd.execCmd method of JP1/IM2 to remotely execute PFM - Manager commands. Therefore, a JP1 user who uses the suggestion function should configure a user mapping in JP1/Base on the PFM - Manager host.
■ When you adopt use case 1 for operation
-
Copy the monitoring template.
Copy the following monitoring template for the alarm table:
-
In PFM - Agent for Platform (Windows)
Original monitoring template: PFM Windows Template Alarms [CPU] 09.00
Destination alarm table name: Windows Template Alarms [CPU] 09.00
-
In PFM - Agent for Platform (UNIX)
Original monitoring template: PFM UNIX Template Alarms [CPU] 09.00
Destination alarm table name: UNIX Template Alarms [CPU] 09.00
-
-
Set up the issuing of a JP1 event.
Edit the following alarm in the destination alarm table to configure it so that a JP1 event is issued when the alarm status is in warning or error.
-
In PFM - Agent for Platform (Windows)
CPU Usage
-
In PFM - Agent for Platform (UNIX)
CPU Per Processor(U)
-
-
Bind the alarm table.
Bind the alarm table you edited to a PFM - Agent for Platform agent.
■ When you adopt use case 2 for operation
If the alarm you want to operate in use case 2 is configured not to issue JP1 events, change its settings so that it issues them.
■ When you adopt use case 3 for operation
-
If the alarm you want to operate in use case 3 is configured not to issue JP1 events, change its settings so that it issues them.
-
If the monitoring suspension function is disabled, you need to enable the monitoring suspension function option.
-
In a multiple-monitoring environment, you need to enable the automatic synchronization options of the settings information for the monitoring suspension function in advance.
(d) Procedure for customizing the suggestion definition file
You can customize the suggestion definition file as follows:
-
Apply the suggestion activation criteria of use case 1 to monitoring items other than the CPU.
-
Change the range of registration dates and times of JP1 events to which the suggestion activation criteria of use cases 1 and 2 are applied.
-
Change the suggestion activation criteria of suggestion information 4 in use case 3.
To customize the file as shown in the above, follow the procedures below.
■ Apply the suggestion activation criteria of use case 1 to monitoring items other than the CPU.
To apply the suggestion activation criteria of use case 1 to non-CPU monitoring items as well as agents other than PFM - Agent for Platform agents, follow the procedure below:
-
Create a new alarm definition.
Create an alarm definition for a given agent, and configure it so that a JP1 event is issued when its alarm status is in warning or error.
-
Bind the alarm table.
Bind the alarm table you created to the agent.
-
Create a new report definition.
Create a real-time report (one agent) for cause investigation when the created alarm is in warning or error status. You need to specify the report display period when the report is displayed, if you create a historical report (one agent).
-
Customize the suggestion definition file (suggestion template).
Customize suggestion information 1 and suggestion information 2.
For details about where and how to customize, see the section describing the procedure for modifying the suggestion definition file in the manual JP1/Performance Management Reference.
■ Change the range of registration dates and times of JP1 events to which the suggestion activation criteria of use cases 1 and 2 are applied.
The suggestion activation criteria of use cases 1 and 2 cover JP1 events registered within 24 hours; however, you can change the range of registration dates and times of target JP1 events.
For details about where and how to customize in the applicable suggestion information, see the section describing the procedure for modifying the suggestion definition file in the manual JP1/Performance Management Reference.
■ Change the suggestion activation criteria of suggestion information 4 in use case 3.
The suggestion activation criteria of suggestion information 4 depend on the number of registered JP1 events indicating that the host has stopped and alarm JP1 events. You can change the range of registration dates and times for target JP1 events and the number of registered events based on the number of issued JP1 events on the system you operate.
If the severity level of the JP1 event issued when the health check result is in Host Not Available status is changed from the default (Error), customize the statusFilter value of health-check JP1 events, which is specified in the suggestion activation criteria with type set to eventCount. For details about the values that can be specified for statusFilter, see the topic describing the suggestion definition file in the manual of JP1/IM2.
- Important
-
For environments with multiple-monitoring, customize the number of registered JP1 events for the suggestion activation criteria assuming that JP1 events will be issued on both the primary and secondary Managers.
For details about where and how to customize in suggestion information 4, see the section describing the procedure for modifying the suggestion definition file in the manual JP1/Performance Management Reference.