[ResponseOps][Alerts][Meta] Stack Alerts page improvements

[umbopepato]

• [x] ⚙️ Stack management label casing (https://github.com/elastic/kibana/pull/184305)

  Will be changed to ⚙️ Stack instead (see next point)

• [x] Feature filter and cell new labels (https://github.com/elastic/kibana/pull/184305)

  As requested by @shanisagiv1 (Rule types spreadsheet) Stack management 👉 Stack Monitoring 👉 Stack Monitoring Machine Learning Rules merged with Stack Rules filter Add a Stack Monitoring feature filter

• [ ] Numeric fields missing from controls editor

  Numeric field types were filtered out in the original implementation, we can remove the filter predicate (make if configurable through a prop) and show them as well in our area.

• [ ] Cannot filter status by Flapping

  This is intended since Flapping is not a kibana.alert.status value, but it's stored in a separate boolean field instead kibana.alert.flapping. To improve this UX we could change the Status cell to show two separate badges instead of one ([Flapping] -> [Active][Flapping]), like we already do for muted alerts:

From https://github.com/elastic/appex-qa-team/issues/153#issuecomment-2061639260 points 3, 4, 5

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[cnasikas]

@umbopepato I noticed that if you have access only to "Stack alerts", you create a rule, and then go to the stack alerts table you get a bunch of 403 toasters. You can see the alerts but you cannot use the filters and controls.

[cnasikas]

I found another bug. The table shows all alerts and then applies the filters (active alerts for example).

https://github.com/elastic/kibana/assets/7871006/9d5f3c7f-aef7-43a4-99df-ec799b68c5fe

[umbopepato]

Thanks for reporting these @cnasikas 👍

@umbopepato I noticed that if you have access only to "Stack alerts", you create a rule, and then go to the stack alerts table you get a bunch of 403 toasters. You can see the alerts but you cannot use the filters and controls.

As discussed separately, a possible improvement for unprivileged users getting 403 toast messages could be to hide the controls bar and show a prompt informing about the necessary permissions (like Security Solution does, but smaller).

I found another bug. The table shows all alerts and then applies the filters (active alerts for example).

This should be the same as https://github.com/elastic/kibana/issues/183412

[cnasikas]

I created the following issue https://github.com/elastic/kibana/issues/186451 for the permissions bug.