Add system test for libbeat internal x-pack monitoring#10645
Merged
ycombinator merged 11 commits intoelastic:masterfrom Feb 11, 2019
ycombinator:libbeat-monitoring-system-test
Merged
Add system test for libbeat internal x-pack monitoring#10645ycombinator merged 11 commits intoelastic:masterfrom ycombinator:libbeat-monitoring-system-test
ycombinator merged 11 commits intoelastic:masterfrom
ycombinator:libbeat-monitoring-system-test
Conversation
3 tasks
Contributor
Author
|
jenkins, test this |
Contributor
Author
|
Please note that this PR just adds a test for existing functionality. I plan to then build upon this test for the functionality being introduced in #9260. |
ruflin
approved these changes
Feb 11, 2019
Contributor
ruflin
left a comment
There was a problem hiding this comment.
LGTM. Comment can be addressed later.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
libbeat has code for shipping x-pack monitoring data to the elasticsearch cluster configured either via
outputs.elasticsearch.*orxpack.monitoring.elasticsearch.*. This cluster then exports the given data to a monitoring cluster, which may be a separate dedicated monitoring cluster or the same cluster that received the data from the beat.Currently there are no system tests to test this x-pack monitoring feature in libbeat. This PR creates such a system test. The test:
mockbeat) to ship data to a cluster defined viaxpack.monitoring.elasticsearch.hosts. Let's call this clusterES1.ES2.ES1's cluster settings to export monitoring data it receives toES2.ES1.mockbeatand waits till it has shipped some monitoring data toES1.ES2and asserts that the expected data was indexed into.monitoring-beats-*indices.