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

[Alerting] [o11y] Determine where to store the index #100681

Closed
chrisronline opened this issue May 26, 2021 · 2 comments
Closed

[Alerting] [o11y] Determine where to store the index #100681

chrisronline opened this issue May 26, 2021 · 2 comments
Labels
blocked Feature:Actions Feature:Alerting Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@chrisronline
Copy link
Contributor

Relates to #98902 (comment)

Blocked: This is currently blocked for the same reasons as #100678

Once we determine the set of metrics that are valuable (see #100675), we want to figure out where the data should live. The obvious first choice is the same cluster which Kibana is talking to, but it might be hard to query the data if the cluster is overwhelmed. The Stack Monitoring solution already has the ability to index data into separate, dedicated cluster for monitoring storage which might be a better long term fit.

@chrisronline chrisronline added blocked Feature:Alerting Feature:Task Manager Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels May 26, 2021
@elasticmachine
Copy link
Contributor

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

@chrisronline
Copy link
Contributor Author

Closing as the new proposal is taking down a different path in the short term

@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
@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
Labels
blocked Feature:Actions Feature:Alerting Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

3 participants