[Stack Monitoring] add back api integration tests and update esArchiver data #126998
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
neptunian
added
the
Team:Infra Monitoring UI - DEPRECATED
|
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
|
@elasticmachine merge upstream |
neptunian
added
release_note:skip
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @neptunian |
matschaffer
approved these changes
Mar 8, 2022
|
@matschaffer Thanks. I just used @klacabane's script https://gist.github.com/klacabane/1bcddbee8c04161ac56d2d1ac2a234e2 as this was all beats data. I've also removed the mappings so it uses the correct ones that come with Kibana. |
|
Ah nice! we should probably get that into a doc somewhere |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
API integration tests for metricbeat were commented out in #119112 (8.1) temporarily and were not commented back in. After putting them back in, a few fail, because we removed
metricbeat-*from the index pattern, but the data in some test archives is stillmetricbeat-*. This PR comments all the tests back in and updates the data to use the ECS metricbeat data EXCEPT /setup. The setup tests are not as straight forward for testing metricbeat data streams because its mixed with legacy monitoring data in order to figure out states of migration (both legacy and datastream data must exist) so these could not be loaded the same way. This will be done in separate PR.No tests fail after updating the archive data.