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

Validate that kibana/status metricset cannot be used with xpack.enabled: true #12264

Merged
merged 2 commits into from
May 24, 2019

Conversation

ycombinator
Copy link
Contributor

@ycombinator ycombinator commented May 24, 2019

The kibana/status metricset doesn't have an x-pack code path (used for stack monitoring). Yet, prior to this PR we would allow users to enable the kibana/status metricset AND set xpack.enabled: true. This would result in unexpected and invalid behavior.

With this PR if this combination is detected, an error is thrown.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/stack-monitoring

@ycombinator ycombinator requested a review from ruflin May 24, 2019 04:52
@ycombinator ycombinator merged commit 0c814f8 into elastic:master May 24, 2019
ycombinator added a commit that referenced this pull request May 25, 2019
….enabled: true (#12264) (#12277)

* Validate that kibana/status metricset cannot be used with xpack.enabled: true

* Adding CHANGELOG entry
ycombinator added a commit that referenced this pull request May 25, 2019
….enabled: true (#12264) (#12276)

* Validate that kibana/status metricset cannot be used with xpack.enabled: true

* Adding CHANGELOG entry
@ycombinator ycombinator deleted the mb-kb-validate-status-xpack branch December 25, 2019 11:18
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
….enabled: true (elastic#12264) (elastic#12276)

* Validate that kibana/status metricset cannot be used with xpack.enabled: true

* Adding CHANGELOG entry
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