-
Notifications
You must be signed in to change notification settings - Fork 42
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
Document how to retain data ILM policies #286
Comments
Lower priority than elastic/integrations#2196 |
This should wait for elastic/uptime#453 to be done, in case that identifies changes to the way we configure data streams to ILM policies. |
This should be based on the implementation in elastic/uptime#462 |
Rather than the original Synthtics Integration, I think we should re-purpose this to do it based on the elastic/uptime#462 implementation (for the Synthetics Service), and then also the new integration we'll get with elastic/uptime#441 |
Updated this issue description as discussed in the docs sync yesterday |
Discussed with @dominiqueclarke about the placement and content, and she suggested
|
Now that we have separate ILM policies for each type of monitor (elastic/uptime#462), monitors running through Elastic Agent that make use of datastreams (which includes the Synthetics Service, and self-managed nodes elastic/uptime#441), we should document how users can customise these to suit their requirements (e.g longer or shorter retentions based on the kind of data).
Considerations:
The text was updated successfully, but these errors were encountered: