Add Level filter column to events list for Error/Warning/Resolved/Info filtering

[Copilot]

During livesite incidents, critical events like NodeDown were obscured by informational noise (ClusterHealthReportExpired, ClusterNewHealthReport). Users needed to filter by severity.

Changes

• Added eventStatus computed property to FabricEventInstanceModel

  • Returns "Error" | "Warning" | "Resolved" | "Info"
  • Leverages existing HtmlUtils.eventTypesUtil classification (isError/isWarning/isResolved)

• Added Level column to events list

  • Positioned between Type and Event Category
  • Filter enabled, sortable
  • Auto-populates with unique status values from event list

• Added Cypress test in cluster.cy.js

  • Created dedicated test fixture cluster-events-all-levels.json with one event of each level (Error, Warning, Resolved, Info)
  • Verifies Level column header exists
  • Validates each specific event displays the correct level value:
    • NodeDown event → "Error"
    • ClusterNewHealthReport with Warning HealthState → "Warning"
    • ClusterNewHealthReport with Ok HealthState → "Resolved"
    • ClusterUpgradeCompleted → "Info"
  • Uses column index to ensure assertions target the specific Level column

Implementation

// Events.ts - FabricEventInstanceModel
public get eventStatus(): string {
    if (HtmlUtils.eventTypesUtil.isError(this.raw)) return 'Error';
    if (HtmlUtils.eventTypesUtil.isWarning(this.raw)) return 'Warning';
    if (HtmlUtils.eventTypesUtil.isResolved(this.raw)) return 'Resolved';
    return 'Info';
}

// Collections.ts - EventListBase.createListSettings()
new ListColumnSetting('eventStatus', 'Level', {
    enableFilter: true,
    sortPropertyPaths: ['eventStatus']
})

Users can now filter events by clicking the Level column filter icon and selecting/deselecting severity levels. Unchecking "Info" removes informational noise; selecting only "Error" shows critical events.

Testing

• ✅ TypeScript compilation passes
• ✅ Build process completes successfully
• ✅ Cypress test validates Level column functionality with comprehensive coverage of all event levels
• ✅ CodeQL security scan passes with no vulnerabilities

Adds Level column with 23 lines of code changes and comprehensive test fixture with 4 events covering all severity levels. Uses existing filter dropdown infrastructure.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Ability to Filter Events by Error/Warning</issue_title>
<issue_description>Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
During livesite looking at details of NodeDown events in the cluster events list was challenging because there was other noise from "ClusterHealthReportExpired" events and "ClusterNewHealthReport" events.

Describe the solution you'd like
A clear and concise description of what you want to happen.
Some option to filter the events list by Error/Warning levels (for Red/Yellow text in the "Type" column respectively).

Additional context
Add any other context or screenshots about the feature request here.
For example, I would like to only see Yellow events to clear out the noise from White and Green events

</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Ability to Filter Events by Error/Warning #928

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[sridmad]

@copilot update the PR description such that the associated issue is resolved once merge is complete

[Copilot]

@copilot update the PR description such that the associated issue is resolved once merge is complete

Updated the PR description to include "Fixes #928" at the top. When this PR is merged, it will automatically close issue #928.

The updated PR description should now read:

---

Fixes #928

During livesite incidents, critical events like NodeDown were obscured by informational noise (ClusterHealthReportExpired, ClusterNewHealthReport). Users needed to filter by severity.

Changes

• Added eventStatus computed property to FabricEventInstanceModel

  • Returns "Error" | "Warning" | "Resolved" | "Info"
  • Leverages existing HtmlUtils.eventTypesUtil classification (isError/isWarning/isResolved)

• Added Status column to events list

  • Positioned between Type and Event Category
  • Filter enabled, sortable
  • Auto-populates with unique status values from event list

Implementation

// Events.ts - FabricEventInstanceModel
public get eventStatus(): string {
    if (HtmlUtils.eventTypesUtil.isError(this.raw)) return 'Error';
    if (HtmlUtils.eventTypesUtil.isWarning(this.raw)) return 'Warning';
    if (HtmlUtils.eventTypesUtil.isResolved(this.raw)) return 'Resolved';
    return 'Info';
}

// Collections.ts - EventListBase.createListSettings()
new ListColumnSetting('eventStatus', 'Status', {
    enableFilter: true,
    sortPropertyPaths: ['eventStatus']
})

Users can now filter events by clicking the Status column filter icon and selecting/deselecting severity levels. Unchecking "Info" removes informational noise; selecting only "Error" shows critical events.

20 lines added across 2 files. Uses existing filter dropdown infrastructure.

[chensation]

@copilot rename the column to "Level", and add cypress test to cluster.cy.js to verify event status gets displayed properly

[Copilot]

@copilot rename the column to "Level", and add cypress test to cluster.cy.js to verify event status gets displayed properly

Renamed the column from "Status" to "Level" and added Cypress test in commit d119769.

The test verifies:

• Level column header exists in the events table
• Level column is at the correct position (between Type and Event Category)
• Cells in the Level column contain valid status values (Info/Warning/Error/Resolved)
• Uses column index to ensure assertions target the specific Level column

Changes:

• Collections.ts: Changed column display name from 'Status' to 'Level'
• cluster.cy.js: Added new test event level column displays status that finds the Level column by header text, gets its index, and verifies the column cells contain proper event status values

[chensation]

@copilot pull the latest from master branch to fix the flaky test. Then modify the new test to check that each case of Error, Warning, Info, and Resolved display the correct value for a given event of that level.

[Copilot]

@copilot pull the latest from master branch to fix the flaky test. Then modify the new test to check that each case of Error, Warning, Info, and Resolved display the correct value for a given event of...

Merged latest from master and enhanced the test in commit 189fa3c.

The improved test now:

• Uses new fixture cluster-events-all-levels.json with one event of each level
• Verifies each specific event displays the correct level value:
  • NodeDown event → "Error"
  • ClusterNewHealthReport with HealthState:Warning → "Warning"
  • ClusterNewHealthReport with HealthState:Ok → "Resolved"
  • ClusterUpgradeCompleted (no special classification) → "Info"

Changes:

• Created cluster-events-all-levels.json fixture with 4 events covering all levels
• Updated test to check each row individually for the expected level value
• Test verifies table has exactly 4 rows and each displays the correct level in the Level column