Skip to content

Alerting TLS requirement should be a blocking action in the UI #61885

@snide

Description

@snide

From a design standpoint we should handle the TLS requirement better. If Alerting does not work until TLS is set up, we should not display create actions for alerts till that section is done.

Off-hand the suggestion would be to use a road block, rather than a warning for these items. Otherwise they confuse what the next steps are. Specifically running through the creation flows lead to dead ends, so we shouldn't be showing the forms.

Also, try not to use buttons for links. Use links for links. The buttons here look like they are toggles. We should telegraph to the user what clicking that button does. "Check the docs for how to set up TLS"...etc.

cc @mdefazio @andreadelrio

image

image

Metadata

Metadata

Assignees

Labels

Feature:AlertingTeam:Platform-DesignTeam Label for Kibana Design Team. Support the Analyze group of plugins.Team:ResponseOpsPlatform ResponseOps team (formerly the Cases and Alerting teams) t//

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions