Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Actionable observability] Make the alert summary widget clickable #141467

Closed
Tracked by #137196
maryam-saeidi opened this issue Sep 22, 2022 · 3 comments · Fixed by #147103
Closed
Tracked by #137196

[Actionable observability] Make the alert summary widget clickable #141467

maryam-saeidi opened this issue Sep 22, 2022 · 3 comments · Fixed by #147103
Assignees
Labels
Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" v8.6.0

Comments

@maryam-saeidi
Copy link
Member

maryam-saeidi commented Sep 22, 2022

📝 Summary

The alert summary widget should be clickable and upon clicking on the number of active or recovered alerts, the user will be redirected to a page with more information.

Questions:

  1. Should this navigation be defined in the component or be provided by the consumer?
    It will be passed to the component by the consumer since we have different alert tabs for different apps.

✅ Acceptance Criteria

  • Make the alert summary widget clickable
@maryam-saeidi maryam-saeidi added Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" v8.6.0 labels Sep 22, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/actionable-observability (Team: Actionable Observability)

@emma-raffenne
Copy link
Contributor

@maryam-saeidi Regarding Q1 where to redirect the user to when they click on the widget, given this component will be integrated in many different pages and contexts (and we can expect more to come in the future), I would recommend to allow the consumer/integrator to configure the redirect URL. A default can/should be provided though.

cc @vinaychandrasekhar @simianhacker

@maryam-saeidi
Copy link
Member Author

@emma-raffenne Yes, my question was before I was aware of having different alert tabs and I will add the possibility of providing a link by the consumer. (I will update the ticket description)
By default, it will not be clickable since the component cannot decide where to send the user with which type of filtering.

maryam-saeidi added a commit that referenced this issue Dec 7, 2022
…maryWidget clickable (#147103)

Resolves #141467

## 📝 Summary

- Added a
[locator](https://docs.elastic.dev/kibana-dev-docs/routing-and-navigation#specifying-state)
for the rule details page
- Made AlertSummaryWidget clickable and implemented the related
navigation for rule details page

## 🧪 How to test
- Create a rule and go to the rule details page
- You should be able to click on all/active/recovered sections in Alert
Summary Widget and upon click going to alert tables with the correct
filter


https://user-images.githubusercontent.com/12370520/205959565-6c383910-763f-4214-9baa-cf191f012de9.mp4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" v8.6.0
Projects
None yet
3 participants