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

[RAM] Alert table should use discover table #166200

Open
XavierM opened this issue Sep 11, 2023 · 2 comments
Open

[RAM] Alert table should use discover table #166200

XavierM opened this issue Sep 11, 2023 · 2 comments
Labels
enhancement New value added to drive a business result Feature:Alerting/RulesManagement Issues related to the Rules Management UX response-ops-mx-backlog ResponseOps MX backlog Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@XavierM
Copy link
Contributor

XavierM commented Sep 11, 2023

We would like to convert our alert table to use the discover table from this PR. @YulNaumenko and her team did a lot of performance testing around this table for security solution use cases. We do believe that this table will also help our alert table for security and observability users. It will be better to have this table following the same architecture as everywhere else in kibana since we will get bug/enhancement for free.

Example of integration => #166104

@XavierM XavierM added enhancement New value added to drive a business result Feature:Alerting/RulesManagement Issues related to the Rules Management UX v8.11.0 labels Sep 11, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 11, 2023
@XavierM XavierM added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Sep 11, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@XavierM
Copy link
Contributor Author

XavierM commented Oct 10, 2023

We believed that the security solution had already integrated this component into their plugin. However, that's not true so we don't believe it would be wise for us to undertake this task, as it would require us to extract a significant amount of functionality from this component that has not yet been implemented. We will wait for this POC to be merged before acting on it.

@XavierM XavierM removed the v8.11.0 label Oct 10, 2023
@cnasikas cnasikas added the response-ops-mx-backlog ResponseOps MX backlog label Oct 29, 2024
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/RulesManagement Issues related to the Rules Management UX response-ops-mx-backlog ResponseOps MX backlog Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

No branches or pull requests

4 participants