Dedicated Rules view for Observability rules

[vinaychandrasekhar]

Describe the feature:
Create a dedicated rules view for managing Observability rules.

1. Shows rules specific to Observability
2. Shows last response status for each rule
3. 'Create rule' flyout shows only Observability rule types for selection
4. Retains Observability context (i.e., left hand navigation pane showing Observability navigation)
5. Clicking 'Manage rules' in the Alerts view brings the user to this new dedicated rules view
6. This new view is included in the left hand navigation pane under "Overview" where Cases and Alerts are currently listed (TBD: is this the correct place to list the alert related links?)

Design work

Figma file
Prototype

Implementation Tickets

• Create new Rule Page under Observability #123580
  • Style EuiBasicTable according to design #126774
  • Refactor Rules Table to use a useFetchRules hook #126775
• Edit and Delete Actions #123581
• Create new rule #127011
• Enable o11y rules feature flag #127622
• Add Snoozed status in the rules table Status column #127434
• Add experimental / tech preview icon on the new Rules management view #127952
• Allowed rule operations for users with read permissions #123585
• Add search functionality in the rules page #127579
• Add filtering #123582
  • Filter per last response #127014
  • Filter per observability rule types #127012
• Show rule type name in the Rule column #127433
• No data screen for rules page #127583
• Move rules menu option under alerts #128435
• Add unit tests for new o11y Rule page #127440
• Whitelist rule feature flag on cloud #124135

[katrin-freihofner]

Design doc
Design issue

[katrin-freihofner]

Open questions

• What should the “last response” column show?
• What does a 'Create rule' flyout for Observability rule types look like? How does it work?
• From a users view, does it make sense that the rules page is available in the solution navigation?

[katrin-freihofner]

As discussed in our meeting I opened the following design issues:
Define navigation and user flow for rules view
Design create rule flyout for Observability rules

[katrin-freihofner]

What we should also be working on is the rules details view.

[simianhacker]

I feel like #119102 should just be a feature of the dedicated rules view instead of seperate epic task.

[jasonrhodes]

@katrin-freihofner / @vinaychandrasekhar do you all mind getting images of the screens we want to focus on for the first "MVP" of this idea and adding them as images to this epic (as opposed to Figma)? That would be a big help to further our refinement of implementation tickets. Thanks!

[katrin-freihofner]

@jasonrhodes I exported and added two example designs to the description. The full design can be found here. Exported images tend to age very quickly, that is why I suggest always referring to the working file (Figma).

@hbharding build a prototype and more screens to show specific interactions and details. Once you have split down the work we can contribute these to the individual engineering issues.

[katrin-freihofner]

Please be aware that some design details are still missing: https://github.com/elastic/observability-design/issues/127

[jasonrhodes]

Some thoughts/related notes about how to query for "observability" rules:

• [Alerting Framework] Create a new rule count/summary endpoint #119226
• [RAC] Add indicator about enabled / disabled rules on the alerts page #116476 (comment)

I'm not sure it's possible to query for "observability", but rather for individual rule types (called alertType still, possibly) ... so we may need to keep a list of observability rule types for this kind of query. It would be great if this was registered somewhere but I don't think it is currently.

[katrin-freihofner]

I'm still working on a couple of details, especially for the rule details view. Please reach out if you have any questions in the meantime and add me to any PRs. I will add any updates here.

[vinaychandrasekhar]

Hi @mgiota - suggestions on priority for remaining tickets. cc @simianhacker

Must-have for 8.2 in priority order:

• Enable o11y rules feature flag #127622 -> in review
• Allowed rule operations for users with read permissions #123585 (and in general, all RBAC functions) -> in review
• Add search functionality in the rules page #127579
• Add Snoozed status in the rules table Status column #127434 (should say "snoozed") -> in review
• Add experimental / tech preview icon on the new Rules management view #127952
• Add unit tests for new o11y Rule page #127440

Nice-to-have for 8.2 in priority order:

• Add refresh button to o11y rules page #127436
• No data screen for rules page #127583 -> in review
• Add filtering #123582
  • Filter per last response #127014
  • Filter per observability rule types #127012 -> in review

Unknown / need more info:

• Implement the License modal for the last response column #127437 (Panagiota to update the description once they get to this)

[fkanout]

@katrin-freihofner, could you help me understand what the tags in the Rules alerts table are representing. I couldn't find any details.

[mgiota]

@fkanout I was wondering the same. I was able to find an answer by looking into the Figma file.

User can specify the tags in the Rule create/edit flyout