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

Document how to retain data ILM policies #286

Closed
andrewvc opened this issue May 24, 2021 · 6 comments · Fixed by elastic/observability-docs#1944
Closed

Document how to retain data ILM policies #286

andrewvc opened this issue May 24, 2021 · 6 comments · Fixed by elastic/observability-docs#1944
Assignees
Labels
enhancement New feature or request

Comments

@andrewvc
Copy link
Contributor

andrewvc commented May 24, 2021

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:

  • Where should the entry point be for this documentation?
    • Monitor Management is a temporary UI, so perhaps we should show how to configure these for PUSH or Synthetics UI based monitors, or those running from self-managed nodes
    • The existing Synthetics Integration will be deprecated and removed, in favour of the self-managed nodes, so probably not worth documenting that workflow
    • Perhaps the existing ILM / policy docs are the best place to highlight this (with a link from the Synthetics docs)
  • Docs should include some indication of how the different types of data for different monitor types have a different storage profile (e.g. we know that the network data can take up the most space, and then screenshots)
@paulb-elastic
Copy link
Contributor

Lower priority than elastic/integrations#2196

@paulb-elastic
Copy link
Contributor

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.

@paulb-elastic
Copy link
Contributor

This should be based on the implementation in elastic/uptime#462

@paulb-elastic
Copy link
Contributor

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

@paulb-elastic paulb-elastic changed the title Document how to retain data with fleet integration and ILM policies Document how to retain data ILM policies May 26, 2022
@paulb-elastic
Copy link
Contributor

Updated this issue description as discussed in the docs sync yesterday

@paulb-elastic
Copy link
Contributor

Discussed with @dominiqueclarke about the placement and content, and she suggested

I think the documentation should either restate the information from the fleet document with a focus on the synthetics data streams, or link to the fleet documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants