12.1.8 Considerations for changing JP1 event levels
Consider changing the event levels associated with JP1 events so that the events can be appropriately categorized during system monitoring.
A JP1 event issued by a particular host or product and forwarded to the integrated manager might have an event level that does not reflect its importance in terms of system operation.
By using the severity changing function, you can change the event levels of JP1 events to realize event management that takes how you use the system into account. You can also assign a blanket event level to events from a particular agent.
|
|
![[Figure]](GRAPHICS/CS061550.GIF)
- Organization of this subsection
(1) Event types that support event level changing
You can change the event level of JP1 events and events in JP1/SES format, except when the severity level is a character string of 256 or more bytes. If JP1/IM is unable to change a severity level as directed, the message KAVB4611-E is output to the integrated trace log file.
(2) Effect on JP1/IM functions
The severity changing function has an effect on various JP1/IM functions. The following table lists the definitions affected by changes to event levels, and indicates which of the event levels you can specify in each function.
|
No. |
Definition |
Event level prior to change |
Event level after change |
|---|---|---|---|
|
1 |
Event acquisition filter |
Y |
N |
|
2 |
View filter |
Y |
Y |
|
3 |
Event receiver filter |
N |
Y |
|
4 |
Severe event definition |
N |
Y |
|
5 |
Event search conditions |
Y |
Y |
|
6 |
Correlation event generation definition |
N |
Y |
|
7 |
Automated action definition |
N |
Y |
|
8 |
Definition for extended event attributes |
N |
Y |
|
9 |
Event guide information |
N |
Y |
|
10 |
Definition for opening monitor windows |
N |
Y |
|
11 |
Mapping definition of the event source host |
Y |
N |
|
12 |
Repeated event condition |
Y |
N |
|
13 |
Display message change definition |
N |
Y |
- Legend:
-
Y: Can be specified.
N: Cannot be specified.
(3) Effect on linked products
The severity changing function has an effect on the products linked with JP1/IM.
The following describes the effects of the severity changing function in the Central Scope and JP1/IM - Rule Operation.
(a) Effects in Central Scope
The Central Scope monitors JP1 events based on their new event levels.
In some cases, changing an event level might cause a status change condition already established for a monitoring node not to match the monitoring condition. To avoid a situation in which the status of a monitoring node does not change as intended, you need to review status change conditions set for the following system-monitoring objects:
-
Agent Monitoring (PFM) system-monitoring objects
-
Resource error event (PFM)
-
Resource warning event (PFM)
-
-
HiRDB Monitoring system-monitoring objects
-
HiRDB emergency event
-
HiRDB alert event
-
HiRDB critical event
-
HiRDB error event
-
HiRDB warning event
-
-
Physical Host Monitoring (System Manager) system-monitoring objects
-
Physical host emergency event
-
Physical host alert event
-
Physical host critical event
-
Physical host error event
-
Physical host warning event
-
For details about system-monitoring objects, see Chapter 4. Lists of System-Monitoring Objects (for Central Scope) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
(b) Effects in JP1/IM - Rule Operation
In a rule startup condition of JP1/IM - Rule Operation, specify the original event level of the JP1 event.