Service Escalation Web GUI Issue

[michael.gabriel]

We recently updated our Nagios XI version to Nagios XI 2024R1.3.3. According to the logs the update went without issues, the only warnings generated were the following: "Warning: Host 'Hostname' has no default contacts or contactgroups defined!". We do however have an odd behavior in the Web GUI. We have Service Escalations defined with the following configuration:

Code: Select all

define serviceescalation {
    # config_name            All - C: Drive Usage - Warning Alerts
    host_name                SERVERNAME
    service_description      C: Drive Usage
    contact_groups           Admins
    first_notification       1
    last_notification        0
    notification_interval    1440
    escalation_period        workhours
    escalation_options       w,r,
}

However when you enter the corresponding page in the Core Configuration Manager (CCM -> Alerting -> Service Escalations), the "Last Notification" field does not display a value:

Nagios Issue.png

If you make any changes to the configuration (i.e., add a host) and click save you get a popup error with the following message "Missing required fields". If you add the last notification value back in it allows you to save the changes, but if you go back into the service escalation afterwards the field is still missing. This requires us to put a value into the field every time we make changes to the service escalation. Thanks in advance for any help you can provide in solving this issue.

System Information:
CentOS Stream (5.14.0-480.el9.x86_64)
Nagios XI Version 2024R1.3.3

[bbahn]

Hello @michael.gabriel,

How did you add this service escalation to Nagios XI? Did you import it through the Nagios XI like can be seen here: Importing Core Configuration Files?

Was this escalation already imported into Nagios XI and working prior to your upgrade to 2024R1.3.3?

[michael.gabriel]

Hi @bbahn,

To answer your questions:

I configured the service escalations through the web GUI Core Configuration Manager, and the escalations existed prior to the upgrade and were working as expected. Doing some further testing on my end, it appears that the service escalations still work as expected, it's mainly an inconvenience on in the GUI at this point.

[gwesterman]

Hi @michael.gabriel,

This is a bug. If you would like to keep track of its status, keep an eye on our changelog. The issue number is #1476.

Thank you!