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

Improve UX for finding documentation for each alert type #75548

Closed
mikecote opened this issue Aug 20, 2020 · 8 comments · Fixed by #81526
Closed

Improve UX for finding documentation for each alert type #75548

mikecote opened this issue Aug 20, 2020 · 8 comments · Fixed by #81526
Assignees
Labels
enhancement New value added to drive a business result Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) UX

Comments

@mikecote
Copy link
Contributor

The documentation for alert types states that For domain-specific alert types, refer to the documentation for that app. but users are still having a hard time finding the documentation related to the alert type presented in the management creation UI.

There may be a few causes for this:

  • The alert type doesn't have documentation
  • There's no centralized place / catalogue in the documentation listing these alert types
  • The UI doesn't point to the docs on how to configure the selected alert type

and others.

@mikecote mikecote added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Aug 20, 2020
@elasticmachine
Copy link
Contributor

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

@mikecote
Copy link
Contributor Author

cc @gchaps, in case you have alternate proposals

@gchaps
Copy link
Contributor

gchaps commented Aug 20, 2020

@mikecote It would be nice to get the information to the user as close as possible to the point of use. Can we include a link in the UI that opens a flyout with the information?

@mikecote
Copy link
Contributor Author

@mikecote It would be nice to get the information to the user as close as possible to the point of use. Can we include a link in the UI that opens a flyout with the information?

@gchaps That would be a good idea. Would the expectation be to open a tab to the documentation website or to copy a snippet of that documentation in a flyout right within Kibana?

@gchaps
Copy link
Contributor

gchaps commented Aug 20, 2020

My preference would be to include a snippet of the documentation in the flyout on the right.

@mikecote mikecote added the enhancement New value added to drive a business result label Aug 26, 2020
@pmuellr
Copy link
Member

pmuellr commented Aug 26, 2020

To require alert types to provide documentation, we can add a required link template string property as part of the alert type, so you couldn't register an alert without doc. Perhaps that would be good for actions as well.

@mikecote mikecote mentioned this issue Sep 16, 2020
36 tasks
@mikecote mikecote self-assigned this Oct 16, 2020
@mikecote mikecote added the UX label Oct 16, 2020
@mikecote
Copy link
Contributor Author

@mikecote to consider #80953 while doing analysis.

@mikecote
Copy link
Contributor Author

mikecote commented Oct 26, 2020

A couple of notes from an offline discussion I had with @gchaps, @mdefazio and @bmcconaghy:


* question mark (?) next to owner means it wasn't decided who yet so TBD
* Any item that touches the UI will wait until @mdefazio has a proposal.

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 Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) UX
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants