Skip to content

Stack Alerts UI Public components don't reside next to their Server components #80958

@gmmorris

Description

@gmmorris

The Stack Alert Types (Index & Geo thresholds) have their public components along side the Alerts & Actions management components for historical reasons.

This means that their Server components and their Public components exist across two plugins: stack_alerts and triggers_actions_ui, which breaks the Kibana Plugin standards and makes it harder to maintain these components as they are different than all other Alert Types in Kibana.

If we align with other plugins (by consolidating both Server and Public components under the single stack_alerts plugin, we can improve maintainability.

Metadata

Metadata

Assignees

Labels

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