Querying Alarms by alarmId leads to a page that loses context on refresh

Description

When using the Alarm Query panel to find an alarm by alarmId, the returned page is opennms/alarm/detail.htm without any arguments to specify the alarmId.

As a result, when the page auto-refreshes there’s no id query parameter and the user is redirected to an error page saying the alarm does not exist.

Steps to reproduce:

  1. Choose a current Alarm that will not be cleared in the next few minutes, copy its alarmId.

  2. In the web UI, navigate to Status → Alarms, and enter the alarmId in the Alarm ID search box.

  3. Click the Search button.

  4. Wait for several minutes until the page auto-refreshes.

Expected results:

The returned page includes the ?id= query string with the alarmId as its argument so that auto-refreshing updates the view of the alarm.

Actual results:

The page auto-refresh results in a “Alarm Cleared or Not Found” message with “Could not find alarm with ID: null” in the body.

Environment

Meridian 2023.1.13-1 on RHEL 8 x86_64

Acceptance / Success Criteria

None

Activity

Show:

Christian Pape June 19, 2024 at 1:52 PM

Fixed

Details

Assignee

Reporter

Sprint

Affects versions

Priority

PagerDuty

Created April 30, 2024 at 9:11 PM
Updated July 8, 2024 at 4:41 PM
Resolved July 2, 2024 at 7:25 AM