G.1 Events (incidents) that are issued by SSO
This section describes events that are issued as incidents.
Note that the following items are displayed as the same information for any event on NNMi.
Type: Management event
Family: SSO
- Organization of this subsection
(1) Resource collection events
(a) Collection status change events
An event is issued when resource collection status changes. In the ssocolmng action definition file, you can specify whether to issue this event. For further information, see 6.3.8 ssocolmng action definition file (ssocolmng.def).
The following table lists the contents of the collection status change events that are displayed in the incident view of NNMi.
Incident name |
Category |
Severity |
Message |
---|---|---|---|
SSO_Resource_Collect_Normal |
Resource |
Normal |
The collection status of $4 (resource-ID: $1) of $3 of $2 is now Collecting. reason: $5 |
SSO_Resource_Collect_Waiting |
Resource |
Normal |
The collection status of $4 (resource-ID: $1) of $3 of $2 is now Standing By. reason: $5 |
SSO_Resource_Collect_Pending |
Resource |
Warning |
The collection status of $4 (resource-ID: $1) of $3 of $2 is now Postponing. reason: $5 |
SSO_Resource_Collect_Complete |
Resource |
Normal |
The collection status of $4 (resource-ID: $1) of $3 of $2 is now Completed. reason: $5 |
SSO_Resource_Collect_Failure |
Resource |
Critical |
The collection status of $4 (resource-ID: $1) of $3 of $2 is now Impossibility. reason: $5 |
The following table lists the contents of the custom incident attributes that are displayed in the incident form of NNMi.
Attribute |
Name |
Value |
---|---|---|
$1 |
resource-ID |
Resource ID |
$2 |
category-name |
Category name |
$3 |
group-name |
Group name |
$4 |
resource-name |
Resource name |
$5 |
reason |
Reason |
$6 |
event-issuer-host-name |
Event issuer host name |
$7 |
source-name |
Monitoring server host name# |
#: If the definition of host name display is set to off (default) in the event destination definition file (ssodest.conf) of the event source SSO, the monitoring server IP address is displayed in place of the monitoring server host name.
(b) Resource status change event
SSO issues an event when the status of a resource is changed. Whether to issue the event is defined in the ssocolmng action definition file. For the definition in the ssocolmng action definition file, see 6.3.8 ssocolmng action definition file (ssocolmng.def).
The following table lists the contents of the resource status change events that are displayed in the incident view of NNMi.
Incident name |
Category |
Severity |
Message |
---|---|---|---|
SSO_Resource_Monitor_Cancel |
Resource |
Normal |
The status of $4: $5 belonging to the $3 group of $2 has changed to Non-monitoring. current-value =$7, instance = $6, warning-threshold = $8, critical-threshold = $9, previous-status = $10 |
SSO_Resource_Monitor_Unknown |
Resource |
Warning |
The status of $4: $5 belonging to the $3 group of $2 has changed to Unknown. current-value =$7, instance = $6, warning-threshold = $8, critical-threshold = $9, previous-status = $10 |
SSO_Resource_Monitor_Normal |
Resource |
Normal |
The status of $4: $5 belonging to the $3 group of $2 has changed to Normal region. current-value =$7, instance = $6, warning-threshold = $8, critical-threshold = $9, previous-status = $10 |
SSO_Resource_Monitor_Warning |
Resource |
Warning |
The status of $4: $5 belonging to the $3 group of $2 has changed to Warning region. current-value =$7, instance = $6, warning-threshold = $8, critical-threshold = $9, previous-status = $10 |
SSO_Resource_Monitor_Critical |
Resource |
Critical |
The status of $4: $5 belonging to the $3 group of $2 has changed to Critical region. current-value =$7, instance = $6, warning-threshold = $8, critical-threshold = $9, previous-status = $10 |
The following table lists the contents of the custom incident attributes that are displayed in the incident form of NNMi.
Attribute |
Name |
Value |
---|---|---|
$1 |
resource-ID |
Resource ID |
$2 |
category-name |
Category name |
$3 |
group-name |
Group name |
$4 |
resource-name |
Resource name |
$5 |
subresource-name |
Subresource name |
$6 |
instance-name |
Instance name |
$7 |
resource-value |
Resource value |
$8 |
warning-threshold |
Warning threshold |
$9 |
critical-threshold |
Critical threshold |
$10 |
state-before-change |
Status before change (non-monitoring: Unm, unknown: Unk, normal: Nor, warning: War, critical: Cri) |
$11 |
event-issuer-host-name |
Event issuer host name#1 |
$12 |
source-name |
Monitoring server host name#2 |
$13 |
subresource-ID |
Subresource ID |
$14 |
occurrence-time |
Incident occurrence time |
$15 |
event-issuer-ip-address |
Event issuer IP address#3 |
$16 |
ssoconsole-port |
Port number of the SSO console |
$17 |
source-ip-address |
Monitoring server IP address |
$18 |
change-my-address |
SSO action IP address#4 |
$19 |
ssoconsole-https-port |
HTTPS communication port number of the SSO console |
#1 This attribute indicates the name of the host at the address in $15.
#2 If the definition of host name display is set to off (default) in the event destination definition file (ssodest.conf) of the event source SSO, the monitoring server IP address is displayed in place of the monitoring server host name.
#3 This attribute indicates the IP address of the physical host or the IP address set by the change-my-address: key. If the NNM action address definition file (ssonnmactaddr.conf) is set, this attribute indicates the monitoring manager's IP address that is set.
#4 This attribute indicates the IP address of the physical host or the IP address set by the change-my-address: key.
(c) Database threshold excess events
When database monitoring is enabled, SSO issues an event if the size of the collection database exceeds a set threshold.
The following table lists the content of the database threshold excess event that is displayed in the incident view of NNMi.
Incident name |
Category |
Severity |
Message |
---|---|---|---|
SSO_Resource_DB_Size_Warning |
Resource |
Warning |
The threshold $1 (Kbytes) was exceeded by the collection database ($4) size. current-value = $2 (Kbytes). user-text: $3 |
The following table lists the contents of the custom incident attributes that are displayed in the incident form of NNMi.
Attribute |
Name |
Value |
---|---|---|
$1 |
user-specified-threshold |
User specified threshold |
$2 |
collection-database-size |
Size of collection database |
$3 |
user-text |
User text |
$4 |
target-server-name |
Target server name |
(d) Database alert/maximum size excess events
When the size of a collection database exceeds the specified alert size, the database alert size excess event is issued. When the size of a collection database exceeds the specified maximum size, the database maximum size excess event is issued. In the ssocolmng action definition file, you can specify whether to issue these events. For further information, see 6.3.8 ssocolmng action definition file (ssocolmng.def).
The following table lists the contents of the database alert/maximum size excess events that are displayed in the incident view of NNMi.
Incident name |
Category |
Severity |
Message |
---|---|---|---|
SSO_Resource_Excess_Alert_DB_Size |
Resource |
Warning |
The collection database of $2:$3:$4 has exceeded the alert size $5 (Mbytes). Now $7, the max size=$6. |
SSO_Resource_Excess_Max_DB_Size |
Resource |
Critical |
The collection database of $2:$3:$4 reached the max size $6 (Mbytes). Now $7, action=$10. |
The following table lists the contents of the custom incident attributes that are displayed in the incident form of NNMi.
Attribute |
Name |
Value |
---|---|---|
$1 |
resource-ID |
Resource ID |
$2 |
category-name |
Category name |
$3 |
group-name |
Group name |
$4 |
resource-name |
Resource name |
$5 |
alert-size |
Alert size |
$6 |
max-size |
Maximum size |
$7 |
collection-database-size |
Collection database size. |
$8 |
event-issuer-host-name |
Event issuer host name |
$9 |
source-name |
Monitoring server host name |
$10 |
action |
Action# |
#: The following table lists the actions.
Action |
Description |
---|---|
did not save collection data. |
Did not save collection data. |
backup collection database. |
Backup collection database. |
(2) Process and service monitoring event
(a) Monitoring status change events
SSO issues an event when process monitoring status is changed. Whether to issue the event is defined in the ssoapmon action definition file. For the definition in the ssoapmon action definition file, see 6.3.7 ssoapmon action definition file (ssoapmon.def).
The following table lists the contents of the monitoring status change events that are displayed in the incident view of NNMi.
Incident name |
Category |
Severity |
Message |
---|---|---|---|
SSO_Process_Monitor_Normal |
Process |
Normal |
The $1's monitored status is changed to Monitoring in progress. reason: $2# |
SSO_Process_Monitor_Complete |
Process |
Normal |
The $1's monitored status is changed to Monitoring completed. reason: $2# |
SSO_Process_Monitor_Failure |
Process |
Warning |
The $1's monitored status is changed to Unmonitorable. reason: $2# |
#: The following table lists the reasons.
Reason |
Description |
---|---|
SNMP error. |
An SNMP communication error occurred when monitoring conditions had been set. |
received event. |
An event was received from APM. |
lost event. |
An event sent from APM was lost. |
health check. |
A health check request was issued. |
The following table lists the contents of the custom incident attributes that are displayed in the incident form of NNMi.
Attribute |
Name |
Value |
---|---|---|
$1 |
application-name |
Application name |
$2 |
reason |
Reason#1 |
$3 |
event-issuer-host-name |
Event issuer host name |
$4 |
source-name |
Monitoring server host name#2 |
#1: The following table lists the reasons.
Reason |
Description |
---|---|
SNMP error. |
An SNMP communication error occurred when monitoring conditions had been set. |
received event. |
An event was received from APM. |
lost event. |
An event sent from APM was lost. |
health check. |
A health check request was issued. |
#2: If the definition of host name display is set to off (default) in the event destination definition file (ssodest.conf) of the event source SSO, the monitoring server IP address is displayed in place of the monitoring server host name.
(b) Process status change events
SSO issues an event when the status of a process is changed. Whether to issue the event is defined in the ssoapmon action definition file. For details on the ssoapmon action definition file, see 6.3.7 ssoapmon action definition file (ssoapmon.def).
The following table lists the contents of the process status change events that are displayed in the incident view of NNMi.
Incident name |
Category |
Severity |
Message |
---|---|---|---|
SSO_Process_Status_Unknown_to_Normal |
Process |
Normal |
$2 of $1 status changed Unknown to Normal region. The number of running processes=$3, upper threshold=$4, lower threshold=$5 |
SSO_Process_Status_Unknown_to_Critical |
Process |
Critical |
$2 of $1 status changed Unknown to Critical region. The number of running processes=$3, upper threshold=$4, lower threshold=$5 |
SSO_Process_Status_Normal_to_Unknown |
Process |
Warning |
$2 of $1 status changed Normal region to Unknown. The number of running processes=$3, upper threshold=$4, lower threshold=$5 |
SSO_Process_Status_Normal_to_Critical |
Process |
Critical |
$2 of $1 status changed Normal region to Critical region. The number of running processes=$3, upper threshold=$4, lower threshold=$5 |
SSO_Process_Status_Critical_to_Unknown |
Process |
Warning |
$2 of $1 status changed Critical region to Unknown. The number of running processes=$3, upper threshold=$4, lower threshold=$5 |
SSO_Process_Status_Critical_to_Normal |
Process |
Normal |
$2 of $1 status changed Critical region to Normal region. The number of running processes=$3, upper threshold=$4, lower threshold=$5 |
The following table lists the contents of the custom incident attributes that are displayed in the incident form of NNMi.
Attribute |
Name |
Value |
---|---|---|
$1 |
application-name |
Application name |
$2 |
process-name |
Process name |
$3 |
the-number-of-running-processes |
The number of running processes |
$4 |
upper-threshold |
Upper threshold |
$5 |
lower-threshold |
Lower threshold |
$6 |
event-issuer-host-name |
Event issuer host name |
$7 |
source-name |
Monitoring server host name# |
#: If the definition of host name display is set to off (default) in the event destination definition file (ssodest.conf) of the event source SSO, the monitoring server IP address is displayed in place of the monitoring server host name.
(c) Service status change events
SSO issues an event when the status of a monitoring service is changed. Whether to issue the event is defined in the ssoapmon action definition file. For details on the ssoapmon action definition file, see 6.3.7 ssoapmon action definition file (ssoapmon.def).
The following table lists the contents of the service status change events that are displayed in the incident view of NNMi.
Incident name |
Category |
Severity |
Message |
---|---|---|---|
SSO_Service_Status_Unknown_to_Normal |
Service |
Normal |
$2 of $1 status changed Unknown to Normal region. A state of operation=$3 |
SSO_Service_Status_Unknown_to_Critical |
Service |
Critical |
$2 of $1 status changed Unknown to Critical region. A state of operation=$3 |
SSO_Service_Status_Normal_to_Unknown |
Service |
Warning |
$2 of $1 status changed Normal region to Unknown. A state of operation=$3 |
SSO_Service_Status_Normal_to_Critical |
Service |
Critical |
$2 of $1 status changed Normal region to Critical region. A state of operation=$3 |
SSO_Service_Status_Critical_to_Unknown |
Service |
Warning |
$2 of $1 status changed Critical region to Unknown. A state of operation=$3 |
SSO_Service_Status_Critical_to_Normal |
Service |
Normal |
$2 of $1 status changed Critical region to Normal region. A state of operation=$3 |
The following table lists the contents of the custom incident attributes that are displayed in the incident form of NNMi.
Attribute |
Name |
Value |
---|---|---|
$1 |
application-name |
Application name |
$2 |
service-name |
Service name |
$3 |
service-status-ja |
Service operating status |
$4 |
service-status-en |
Service operating status |
$5 |
event-issuer-host-name |
Event issuer host name |
$6 |
source-name |
Monitoring server host name# |
#: If the definition of host name display is set to off (default) in the event destination definition file (ssodest.conf) of the event source SSO, the monitoring server IP address is displayed in place of the monitoring server host name.
(d) Application status change events
SSO issues an event when the status of an application is changed. Whether to issue the event is defined in the ssoapmon action definition file. For details on the ssoapmon action definition file, see 6.3.7 ssoapmon action definition file (ssoapmon.def).
The following table lists the contents of the application status change events that are displayed in the incident view of NNMi.
Incident name |
Category |
Severity |
Message |
---|---|---|---|
SSO_Application_Status_Unknown_to_Normal |
Application |
Normal |
$1 status changed Unknown to Normal region. |
SSO_Application_Status_Unknown_to_Warning |
Application |
Warning |
$1 status changed Unknown to Precaution region. |
SSO_Application_Status_Unknown_to_Critical |
Application |
Critical |
$1 status changed Unknown to Critical region. |
SSO_Application_Status_Normal_to_Unknown |
Application |
Warning |
$1 status changed Normal to Unknown region. |
SSO_Application_Status_Normal_to_Warning |
Application |
Warning |
$1 status changed Normal to Precaution region. |
SSO_Application_Status_Normal_to_Critical |
Application |
Critical |
$1 status changed Normal to Critical region. |
SSO_Application_Status_Warning_to_Unknown |
Application |
Warning |
$1 status changed Precaution to Unknown region. |
SSO_Application_Status_Warning_to_Normal |
Application |
Normal |
$1 status changed Precaution to Normal region. |
SSO_Application_Status_Warning_to_Critical |
Application |
Critical |
$1 status changed Precaution to Critical region. |
SSO_Application_Status_Critical_to_Unknown |
Application |
Warning |
$1 status changed Critical to Unknown region. |
SSO_Application_Status_Critical_to_Normal |
Application |
Normal |
$1 status changed Critical to Normal region. |
SSO_Application_Status_Critical_to_Warning |
Application |
Warning |
$1 status changed Critical to Precaution region. |
The following table lists the contents of the custom incident attributes that are displayed in the incident form of NNMi.
Attribute |
Name |
Value |
---|---|---|
$1 |
application-name |
Application name |
$2 |
event-issuer-host-name |
Event issuer host name |
$3 |
source-name |
Monitoring server host name# |
#: If the definition of host name display is set to off (default) in the event destination definition file (ssodest.conf) of the event source SSO, the monitoring server IP address is displayed in place of the monitoring server host name.
(e) Process and service monitoring failure events
If the unknown event to be issued when a failure of communication with APM is detected is suppressed by setting, SSO issues a process and service monitoring failure event in place of the unknown event. Whether to issue the process and service monitoring failure event is defined in the ssoapmon action definition file. For details on the ssoapmon action definition file, see 6.3.7 ssoapmon action definition file (ssoapmon.def).
The following table lists the contents of the process and service monitoring failure events that are displayed in the incident view of NNMi.
Incident name |
Category |
Severity |
Message |
---|---|---|---|
SSO_Process_Agent_Stop |
Process |
Warning |
Agent for Process has stopped. |
SSO_Process_Agent_NotCommunicate |
Process |
Critical |
It cannot communicate with Agent for Process. reason: $3# |
#: The following table lists the reasons.
Reason |
Description |
---|---|
SNMP error. |
An SNMP communication error occurred when monitoring conditions had been set. |
received event. |
An event was received from APM. |
lost event. |
An event sent from APM was lost. |
health check. |
A health check request was issued. |
The following table lists the contents of the custom incident attributes that are displayed in the incident form of NNMi.
Attribute |
Name |
Value |
---|---|---|
$1 |
monitoring-server-host-name |
Host name of monitoring target server |
$2 |
monitoring-server-ip-address |
IP address of monitoring target server |
$3 |
reason |
Reason#1 |
$4 |
event-issuer-host-name |
Event issuer host name |
$5 |
source-name |
Monitoring server host name#2 |
#1: The following table lists the reasons.
Reason |
Description |
---|---|
SNMP error. |
An SNMP communication error occurred when monitoring conditions had been set. |
received event. |
An event was received from APM. |
lost event. |
An event sent from APM was lost. |
health check. |
A health check request was issued. |
#2: If the definition of host name display is set to off (default) in the event destination definition file (ssodest.conf) of the event source SSO, the monitoring server IP address is displayed in place of the monitoring server host name.