-
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
Remove experimental log message when xpack.enabled flag is set #10222
Conversation
Pinging @elastic/stack-monitoring |
3e76033
to
89f00e2
Compare
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
We should probably also double down on the docs around this feature (if not already the case). Blog post? There we could also explain the reasoning around this change and the technical advantages.
89f00e2
to
7d11734
Compare
@ruflin it looks like the Windows jobs in Jenkins were aborted. I'm guessing this is intentional? If so, given that the other jobs were successful and Travis is green, are you good with me merging this PR? |
@ruflin Yes, I'm good to go. I aborted the windows build as they couldn't keep up and stalled our builds. |
The Elasticsearch and Kibana Metricbeat modules support an
xpack.enabled
flag. This flag's value defaults tofalse
, causing these modules to index their data intometricbeat-*
indices, as is normal with all other Metricbeat modules.However, we want to use these modules for Stack Monitoring as well. Concretely, this means that these modules' data would need to be indexed into
.monitoring-*
indices instead ofmetricbeat-*
indices. This change of indexing target is enabled by settingxpack.enabled: true
.Until this PR, setting
xpack.enabled: true
and the code path that it enabled was marked as experimental. Log messages in the Metricbeat logs would inform the users as such.This PR removes these log messages and thus makes the use of this flag as GA. It also documents this flag in the modules' configuration yaml files.