According to the documentation a number should be output here.
The current state (0 = OK, 1 = WARNING, 2 = CRITICAL, 3 = UNKNOWN)
At least that’s how I understand it. But the output is not the integer but OK, WARNING…
What does the object last_state output? If I have a service check 1/1 the last_state is always OK, but if I have a service 1/3 the last_state seems to be the softstate.
Therefore I wanted to change to the object last_hard_state.
With the Object last_hard_state it is different. Here the integer is output. Only what surprises me, that always 2 (CRITICAL) is output, although the service stood before in the hard state OK.
Am I misunderstanding this now or is it a bug?
Zustands-Änderung (Hard)
ALARM_IC_CONNECT_FAIL
auf
hostname.tld (Sentinel - 111.111.111.111)
am Mar 23 23:10
CRITICAL - NICE: Interactions Center failed to connect to <remote Component type> <remote component name> (TrapEvent: niceSentinelAlarmICConnectFail - niceSentinelAlarmServiceEffect: High Risk Of Recording Loss - niceSentinelAlarmUpdateTime: No data available - niceSentinelAlarmTraps: 1109 - niceSentinelAlarmDescription: Interactions Center failed to connect to Logger - niceSentinelAlarmClearTime: 010101000000 - niceSentinelAlarmComponentType: usqn3pwicn2.sd01.unicreditgroup.eu - ic cluster - niceSentinelAlarmComponentLocation: 230323231015 - niceSentinelAlarmOperation: 1 - niceSentinelAlarmSeverity: 3 - niceSentinelAlarmAckTime: 010101000000 - niceSentinelAlarmAdditionalInfoLink: No data available - niceSentinelAlarmComponentDNS: UniCredit Production - Master Site - niceSentinelAlarmClearingMethod: Interactions Center - niceSentinelAlarmAdditionalInfo: Additional Info: {Board=}, {Internal Component=Interactions Center}{Other=} - niceSentinelAlarmComponentIP: usqn3pwicn2.sd01.unicreditgroup.eu - niceSentinelAlarmOpenTime: 230323231024 - niceSentinelAlarmMetricName: No data available - niceSentinelAlarmMetricValue: No data available - niceSentinelAlarmVersion: 6.3 - niceSentinelAlarmDisplayName: 123.123.123)
Zustands-Änderung (Hard)
ALARM_IC_CONNECT_FAIL
auf
hostname.tld (Sentinel - 111.111.111.111)
am Mar 23 22:22
CRITICAL - NICE: Interactions Center failed to connect to <remote Component type> <remote component name> (TrapEvent: niceSentinelAlarmICConnectFail - niceSentinelAlarmDisplayName: 123.123.123 - niceSentinelAlarmMetricValue: No data available - niceSentinelAlarmVersion: 6.3 - niceSentinelAlarmUpdateTime: No data available - niceSentinelAlarmComponentIP: usqn3pwicn2.sd01.unicreditgroup.eu - niceSentinelAlarmMetricName: No data available - niceSentinelAlarmClearTime: 010101000000 - niceSentinelAlarmDescription: Interactions Center failed to connect to Logger - niceSentinelAlarmComponentLocation: 230323222153 - niceSentinelAlarmAdditionalInfoLink: No data available - niceSentinelAlarmServiceEffect: High Risk Of Recording Loss - niceSentinelAlarmComponentDNS: UniCredit Production - Master Site - niceSentinelAlarmTraps: 1109 - niceSentinelAlarmAdditionalInfo: Additional Info: {Board=}, {Internal Component=Interactions Center}{Other=} - niceSentinelAlarmAckTime: 010101000000 - niceSentinelAlarmOperation: 1 - niceSentinelAlarmClearingMethod: Interactions Center - niceSentinelAlarmComponentType: usqn3pwicn2.sd01.unicreditgroup.eu - ic cluster - niceSentinelAlarmSeverity: 3 - niceSentinelAlarmOpenTime: 230323222159)
Service hat sich erholt
ALARM_IC_CONNECT_FAIL
auf
hostname.tld (Sentinel - 111.111.111.111)
vor 2d 0h
ok
I have to say that we have set Volatile = true for the passive check to see all further traps in the history. If I set this to false we only see the first trap that changes the status.
I described the problem a long time ago here: Notifications for passive services
With the passive check I have tried several things. The problem is exactly as I described it in the ticket.