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

Provide a viewInApp short URL for alerts #87993

Open
timroes opened this issue Jan 12, 2021 · 2 comments
Open

Provide a viewInApp short URL for alerts #87993

timroes opened this issue Jan 12, 2021 · 2 comments
Labels
enhancement New value added to drive a business result estimate:small Small Estimated Level of Effort Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting NeededFor:DataDiscovery NeededFor:VisEditors Project:MoreRuleTypes Alerting team project for providing more ways to construct rules. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@timroes
Copy link
Contributor

timroes commented Jan 12, 2021

It would be nice to have a URL from the alerting framework to not only view the alert, but triggers its viewInApp mode, i.e. I would like to have a URL like http://kibana.team/alerts/<id>/viewInApp that will open that alert inside the actual app, e.g. if it was a Discover alert it should jump to the corresponding discover view, that you would also go to, when using the "view in app" feature on the alert's detail page.

Why is this relevant? Why can't we simply use the actual link to discover e.g. in the message template? The problem is that the "view in app" links from the classical Kibana applications (Discover, Visualize, Dashboard) might be a) very long and b) contain characters that we know are not parsed well in all messaging tools, since they contain the full state containing e.g. parantheses and commans. Meaning that if we would allow the user to inject that URL into a message, the link might actually not be clickable when they receive the message. Having a unified short link from the alerting framework would solve both issues. We'd always have nice short links and we can guarantee they are always parseable in all tools.

Also we can have this as a shared parameter in all connectors/alert types, thus we don't need every alert type to inject it's backlink URL with a potentially different parameter name and users might get confused why they'd need to use Go to {{backlink}} to view results in an Discover alert, but Go to {{link}} in a Lens alert.

@timroes timroes added enhancement New value added to drive a business result Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) NeededFor:KibanaApp labels Jan 12, 2021
@elasticmachine
Copy link
Contributor

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

@mikecote
Copy link
Contributor

mikecote commented Feb 5, 2021

Moving from 7.x - Candidates to 8.x - Candidates (Backlog) after the latest 7.x planning session.

@gmmorris gmmorris added Feature:Alerting Project:MoreRuleTypes Alerting team project for providing more ways to construct rules. Feature:Alerting/RulesManagement Issues related to the Rules Management UX labels Jun 30, 2021
@gmmorris gmmorris added the loe:medium Medium Level of Effort label Jul 14, 2021
@gmmorris gmmorris added the estimate:small Small Estimated Level of Effort label Aug 18, 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result estimate:small Small Estimated Level of Effort Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting NeededFor:DataDiscovery NeededFor:VisEditors Project:MoreRuleTypes Alerting team project for providing more ways to construct rules. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

No branches or pull requests

5 participants