-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] event log should work with data streams #62677
Labels
estimate:needs-research
Estimated as too large and requires research to break down into workable issues
Feature:EventLog
Project:Serverless MVP
R&D
Research and development ticket (not meant to produce code, but to make a decision)
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
pmuellr
added
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
v7.8.0
labels
Apr 6, 2020
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
gmmorris
added
the
loe:needs-research
This issue requires some research before it can be worked on or estimated
label
Jul 14, 2021
gmmorris
added
R&D
Research and development ticket (not meant to produce code, but to make a decision)
estimate:needs-research
Estimated as too large and requires research to break down into workable issues
labels
Aug 13, 2021
gmmorris
removed
the
loe:needs-research
This issue requires some research before it can be worked on or estimated
label
Sep 2, 2021
2 tasks
mikecote
moved this from Todo
to In Progress
in AppEx: ResponseOps - Execution & Connectors
Apr 27, 2023
As discussed in #154266, this will be required for the Serverless offering. |
pmuellr
added a commit
to pmuellr/kibana
that referenced
this issue
May 25, 2023
…nd aliases resolves elastic#62677
mikecote
moved this from In Progress
to In Review
in AppEx: ResponseOps - Execution & Connectors
May 30, 2023
github-project-automation
bot
moved this from In Review
to Done
in AppEx: ResponseOps - Execution & Connectors
Jun 7, 2023
pmuellr
added a commit
that referenced
this issue
Jun 7, 2023
resolves #62677 Changes event log from using indices, aliases, and ILM manually, to using data streams.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
estimate:needs-research
Estimated as too large and requires research to break down into workable issues
Feature:EventLog
Project:Serverless MVP
R&D
Research and development ticket (not meant to produce code, but to make a decision)
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Kibana version: 7.8.0
There is an upcoming feature for elasticsearch called data streams that are a good fit for the event log indices. Other features are planning to use them, and starting to make some architectural changes for that, like apm.
Not sure if this will also be of any use, but se should also take a look at Elastic Package Manager to see if there is anything that would be helpful to us there. At first glance, I'd say no, but we may want to look at the naming conventions anyway.
The text was updated successfully, but these errors were encountered: