[Telemetry][API Integration tests] Ensure .kibana index exists #76662
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
afharo
added
v8.0.0
release_note:skip
afharo
force-pushed
the
telemetry/api-integration-tests/ensure-.kibana-index
branch
from
df0e4be to
b2f6d27
Compare
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
afharo
deleted the
telemetry/api-integration-tests/ensure-.kibana-index
branch
afharo
added a commit
that referenced
this pull request
Sep 10, 2020
…76662) (#77157) Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
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.
Summary
This PR ensures the
.kibanaindex exists before testing the telemetry and/api/statsendpoints. Both of them useusageCollectionand most collectors are reading from that index, leading to failures in the logs that can confuse us when troubleshooting any broken tests.Checklist
Delete any items that are not applicable to this PR.
For maintainers