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.

Sign up for GitHub

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

Jump to bottom

Project: Unified architecture and experience #89673

Closed
mikecote opened this issue Jan 29, 2021 · 2 comments
Closed

Project: Unified architecture and experience #89673

mikecote opened this issue Jan 29, 2021 · 2 comments
Assignees
@mikecote
Labels
Meta Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Jan 29, 2021 •
edited
Loading

Mission: This project aims to consolidate rule definition and data-based alerts and develop a unified experience.

Roadmap
Linked issues
Company theme: Solution-first
Kibana theme: Actionable Kibana

General ideas:

  • The outcome from the “Unified architecture” workstream
  • Creating a first-class application (outcome from “Rules Workstream”)
    • Splitting and cleaning of the triggers_actions_ui code
    • Updated UIs
    • Updated terminology

Alerts as data

Rules and Alerts consolidation

Unified Experience

  • Part of the unified experience is to align the terminology used across stack and solutions. We are tracking these efforts for the alerting APIs and UIs in New alerting terminology #90375.
@mikecote mikecote added Meta Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. labels Jan 29, 2021
@elasticmachine
Copy link
Contributor

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

@mikecote mikecote self-assigned this Jan 29, 2021
@ymao1
Copy link
Contributor

ymao1 commented Dec 3, 2021

Given that we have kicked off new projects, closing due to staleness.

@ymao1 ymao1 closed this as completed Dec 3, 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
Assignees

@mikecote mikecote

Labels
Meta Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kobelb @mikecote @ymao1 @elasticmachine