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

[esArchiver] support archiving of data streams #98366

Closed
neptunian opened this issue Apr 26, 2021 · 3 comments
Closed

[esArchiver] support archiving of data streams #98366

neptunian opened this issue Apr 26, 2021 · 3 comments
Labels
Team:Operations Team label for Operations Team

Comments

@neptunian
Copy link
Contributor

neptunian commented Apr 26, 2021

When trying to write a functional test for Metrics UI, I archived the data specifying .ds-metrics-*. This archives the correct indices, though it does not archive the associated data stream. When the index is recreated using esArchiver load the indices are created without the relative data stream. This is a problem because the view I need to test in the metrics UI queries with the index pattern metrics-*, metricbeat-* which matches the data stream name so no data is returned.

@neptunian neptunian added the Team:Operations Team label for Operations Team label Apr 26, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@spalger
Copy link
Contributor

spalger commented Apr 26, 2021

I would expect that something like node scripts/es_archiver save metrics-8.0.0 would detect that the index is an alias controlled by a data stream, archive the necessary template, and then archive all the docs from the data stream associated with the metrics-8.0.0 alias so that the docs could be indexed by a newly created data stream on load.

@jbudz
Copy link
Member

jbudz commented Jun 15, 2021

Closing this out as a duplicate of #69061

@jbudz jbudz closed this as completed Jun 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

4 participants