Skip to content
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

Merged
merged 3 commits into from
Jan 23, 2019

Conversation

ycombinator
Copy link
Contributor

@ycombinator ycombinator commented Jan 21, 2019

The Elasticsearch and Kibana Metricbeat modules support an xpack.enabled flag. This flag's value defaults to false, causing these modules to index their data into metricbeat-* 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 of metricbeat-* indices. This change of indexing target is enabled by setting xpack.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.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/stack-monitoring

@ycombinator ycombinator requested a review from a team as a code owner January 21, 2019 15:54
@ycombinator ycombinator force-pushed the mb-stack-xp-flag branch 2 times, most recently from 3e76033 to 89f00e2 Compare January 21, 2019 16:25
Copy link
Member

@ruflin ruflin left a 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.

@ycombinator
Copy link
Contributor Author

@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
Copy link
Member

ruflin commented Jan 23, 2019

@ruflin Yes, I'm good to go. I aborted the windows build as they couldn't keep up and stalled our builds.

@ycombinator ycombinator merged commit bb535f9 into elastic:master Jan 23, 2019
@ycombinator ycombinator removed the needs_backport PR is waiting to be backported to other branches. label Jan 23, 2019
ycombinator added a commit to ycombinator/beats that referenced this pull request Jan 23, 2019
…ic#10222)

* Remove experimental log message when xpack.enabled flag is set

* Add CHANGELOG entry

* Generate docs

(cherry picked from commit bb535f9)
ycombinator added a commit that referenced this pull request Jan 23, 2019
… (#10282)

* Remove experimental log message when xpack.enabled flag is set

* Add CHANGELOG entry

* Generate docs

(cherry picked from commit bb535f9)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants