-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add system test for libbeat internal x-pack monitoring #10645
Add system test for libbeat internal x-pack monitoring #10645
Conversation
jenkins, test this |
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Comment can be addressed 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
.mockbeat
and waits till it has shipped some monitoring data toES1
.ES2
and asserts that the expected data was indexed into.monitoring-beats-*
indices.