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

[Trigger Actions UI] Improve alert instances view by having instance name, tags #82707

Closed
shahzad31 opened this issue Nov 5, 2020 · 3 comments
Labels
discuss estimate:small Small Estimated Level of Effort Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) UX

Comments

@shahzad31
Copy link
Contributor

Describe the feature:

Alert UI has a nice instance view which displays alerts instances as a table,

right now instance can only an id , which is then displayed in table, and since that instance id is also used in api, it can't contain for example a url value, i propose that we allow adding few additional fields into instance, like name and tags, so that instance can become more identifiable for user to act like muting them.

image

Describe a specific use case for the feature:
User can identify alerts by instance id, but in some cases those are not really useful, this is in part motivated by this user enhancement request here #80932

@shahzad31 shahzad31 changed the title [Trigger Actions UI] Improve alert instances view [Trigger Actions UI] Improve alert instances view by having instance name, tags Nov 5, 2020
@shahzad31 shahzad31 added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Nov 5, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@pmuellr
Copy link
Member

pmuellr commented Nov 5, 2020

I think this is a DUP of #64268, which we ended up closing. Happy to keep that closed and have this open as the new version of the enhancement request, especially as it suggests adding even more data to instances (eg, tags).

@gmmorris gmmorris added the Feature:Alerting/RulesManagement Issues related to the Rules Management UX label Jul 1, 2021
@gmmorris gmmorris added the loe:medium Medium Level of Effort label Jul 14, 2021
@gmmorris gmmorris added UX estimate:small Small Estimated Level of Effort labels Aug 16, 2021
@gmmorris gmmorris removed the loe:medium Medium Level of Effort label Sep 2, 2021
@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
@shahzad31
Copy link
Contributor Author

closing since , i don't see any more activity or need i guess

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss estimate:small Small Estimated Level of Effort Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) UX
Projects
No open projects
Development

No branches or pull requests

6 participants