Skip to content

NMS-20120: Path Outages tab - #8712

Open
joseanesONMS wants to merge 3 commits into
jira/NMS-20100-notifications-pagefrom
jira/NMS-20120-path-outages
Open

NMS-20120: Path Outages tab#8712
joseanesONMS wants to merge 3 commits into
jira/NMS-20100-notifications-pagefrom
jira/NMS-20120-path-outages

Conversation

@joseanesONMS

Copy link
Copy Markdown

NMS-20120 (NMS-20100 epic): adds the Path Outages tab to the Configure Notifications dialog. Stacked on #8709, so this PR shows only its own commit.

  • Tab with the list of configured critical paths and an apply/clear flow driven by a filter rule with a node-count preview.
  • Storage is and stays the pathoutage table; the endpoints mirror the legacy NotificationWizardServlet semantics, including clearing the path when the critical IP is blank.
  • Replaces fork PR NMS-20100: Path Outages tab #8708.

@joseanesONMS

Copy link
Copy Markdown
Author

@marshallmassengill review requested — stacks on #8709 (only the top commit is new here).

@joseanesONMS
joseanesONMS force-pushed the jira/NMS-20120-path-outages branch from 15d739a to e4746e4 Compare July 30, 2026 21:59
@joseanesONMS joseanesONMS reopened this Jul 30, 2026
@joseanesONMS
joseanesONMS force-pushed the jira/NMS-20120-path-outages branch 3 times, most recently from 0439cf2 to 89e6936 Compare August 1, 2026 02:24

@marshallmassengill marshallmassengill left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor stuff on this one... it's actually shockingly self-contained.

  • Tab opens pre-armed to clear every node. PathOutagesTab.vue:228-229. rule defaults to IPADDR IPLIKE ..., blank criticalIp makes the button "Clear Critical Path". Start rule empty (as was the case with legacy behavior).
  • Confirmation count is nodes matching the rule, not nodes with a path. PathOutagesTab.vue:250. Says 4823 when 3 rows delete. Count existing paths in the preview.
  • Tab loader returns literal true. ConfigureNotificationsDialog.vue:95. Failed GET latches loaded, never retries. Return null from getPathOutages on error.
  • Only raw JDBC in the REST module; PathOutageDao has full CRUD plus getAllCriticalPaths().
  • isBlank dead again. NotificationConfigRestService.java:230.

@joseanesONMS
joseanesONMS requested a review from synqotik August 3, 2026 13:59
@joseanesONMS
joseanesONMS force-pushed the jira/NMS-20120-path-outages branch 2 times, most recently from 24c0485 to b28131f Compare August 3, 2026 17:13
Adds the Path Outages tab: the list of configured critical paths and the
apply/clear flow driven by a filter rule with a node-count preview, in
place of the legacy notification wizard pages. Storage is and stays the
pathoutage table; the endpoints mirror the legacy NotificationWizardServlet
semantics, including clearing the path when the critical IP is blank.
Depends on the Notifications page base PR.
The node-filter rule now starts empty instead of IPADDR IPLIKE *.*.*.*, so the
tab no longer opens pre-armed to clear the critical path for every node. The
clear confirmation counts only the nodes that currently have a critical path and
match the rule, not every node the rule selects, so it no longer claims thousands
when a handful of rows will change. The path-outages tab loader now propagates a
real success flag — getPathOutages returns null on error and the store reports
false — so a failed load retries instead of latching the tab empty.

Also drops the unused isBlank helper from NotificationConfigRestService.
Migrate the Path Outages tab onto the Onms-* seam wrappers (table,
chip, buttons, inputs, select) so the page passes the
no-direct-primevue lint rule; iftalabel stays on PrimeVue as it has no
wrapper. Markup and behaviour are unchanged.
@joseanesONMS
joseanesONMS force-pushed the jira/NMS-20120-path-outages branch from b28131f to 2228c22 Compare August 3, 2026 21:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants