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

Always extract monitoring.cluster_uuid setting from Beat config #17420

Merged
merged 3 commits into from
Apr 3, 2020

Conversation

ycombinator
Copy link
Contributor

@ycombinator ycombinator commented Apr 1, 2020

What does this PR do?

This PR always parses out the value of the monitoring.cluster_uuid setting, regardless of whether monitoring.enabled is set or not.

Prior to this PR, if a user explicitly set monitoring.enabled to false and also set monitoring.cluster_uuid to some value, the latter setting's value would not be parsed out. However, if the user just omitted the monitoring.enabled setting while setting monitoring.cluster_uuid to some value, the latter setting's value would be parsed out. This behavior is buggy as the default value of the monitorig.enabled setting is false so explicitly setting it as such or omitting that setting altogether should result in the same behaviors.

Why is it important?

This setting's value (if this setting is set) must always be exposed in the GET /state Beats API, as this is used by the Metricbeat beat module to monitor Beats.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

@ycombinator ycombinator added the Team:Services (Deprecated) Label for the former Integrations-Services team label Apr 1, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations-services (Team:Services)

@ycombinator ycombinator merged commit e3bb760 into elastic:master Apr 3, 2020
@ycombinator ycombinator deleted the lb-mon-cluster-uuid-bugfix branch April 3, 2020 14:59
ycombinator added a commit that referenced this pull request Apr 3, 2020
…#17420) (#17476)

* Always extract monitoring.cluster_uuid setting from Beat config (#17420)

* Pass monitoring.* config object

* Adding CHANGELOG entry

* Adding system test

* CHANGELOG grooming
ycombinator added a commit that referenced this pull request Apr 3, 2020
…) (#17475)

* Pass monitoring.* config object

* Adding CHANGELOG entry

* Adding system test
ycombinator added a commit that referenced this pull request Apr 3, 2020
…) (#17474)

* Pass monitoring.* config object

* Adding CHANGELOG entry

* Adding system test
@ycombinator ycombinator removed the needs_backport PR is waiting to be backported to other branches. label Apr 3, 2020
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…tic#17420) (elastic#17475)

* Pass monitoring.* config object

* Adding CHANGELOG entry

* Adding system test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Team:Services (Deprecated) Label for the former Integrations-Services team v7.6.3 v7.7.0 v7.8.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

monitoring.cluster_uuid setting not being exposed in GET /state API when monitoring.enabled: false is set
4 participants