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

[UI] Alert details page #51546

Closed
mikecote opened this issue Nov 23, 2019 · 5 comments · Fixed by #55671
Closed

[UI] Alert details page #51546

mikecote opened this issue Nov 23, 2019 · 5 comments · Fixed by #55671
Assignees
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.7.0

Comments

@mikecote
Copy link
Contributor

mikecote commented Nov 23, 2019

This Issue refers to the top half of the Details page:

  1. The top bar (mute/enable, edit actions)

2nd part is handled by #56280.
3rd part is handled by #55424 once the Event Log API is ready.

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-stack-services (Team:Stack Services)

@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@mikecote mikecote changed the title [UI] Alert details page with activity log [UI] Alert details page with alert instances Dec 17, 2019
@gmmorris gmmorris changed the title [UI] Alert details page with alert instances [UI] Alert details page Jan 21, 2020
@mdefazio
Copy link
Contributor

@gmmorris Here are the designs: https://www.figma.com/file/qw5Zge4UdtxawSU6vWVgwM/Alerting-Design?node-id=0%3A1

@gmmorris
Copy link
Contributor

I’ve split the Alert Details Page into 3 separate issues:
The top bar which is almost ready for review #51546
The chart which is waiting on Patrick’s researchhttps://github.com//issues/56280
The Instances which is waiting on the Event Log API #55424

I broke these apart to make it easier for us to do short lived easy to integrate branches.
The one open question I have is about the View in App link which I’m not yet sure how we want to implement.
Does anyone have any ideas for how we might want to link an Alert to an originating App?

@alexfrancoeur
Copy link

I feel like we should be able to link out to the application for the timeframe of the alert. If it's closed, we have a complete start and end time. If it's open, we have a start time and the end time would be now. I wonder if by alert type definition or alert instances triggered, we can apply filters as part of the URL as well.

@gmmorris
Copy link
Contributor

I feel like we should be able to link out to the application for the timeframe of the alert. If it's closed, we have a complete start and end time. If it's open, we have a start time and the end time would be now. I wonder if by alert type definition or alert instances triggered, we can apply filters as part of the URL as well.

To clarify - this is about linking to the Alert Details page, not to the Solution, right?
Regarding linking to the Solution, would love input on the discussion here: #56298

@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.7.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants