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

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

Closed
ycombinator opened this issue Mar 2, 2020 · 2 comments · Fixed by #17420
Assignees
Labels
bug Feature:Stack Monitoring good first issue Indicates a good issue for first-time contributors libbeat Team:Services (Deprecated) Label for the former Integrations-Services team

Comments

@ycombinator
Copy link
Contributor

Observed in 8.0.0 / master as well as 7.6.0.

Interestingly, if the monitoring.enabled setting is left out entirely, the value of monitoring.cluster_uuid does show up in the GET /state API response.

So we need monitoring.enabled: false to behave the same as the monitoring.enabled setting not being specified at all. In either case, if monitoring.cluster_uuid is set, it's value should show up in the GET /state API response.

@ycombinator ycombinator added bug libbeat good first issue Indicates a good issue for first-time contributors Feature:Stack Monitoring labels Mar 2, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/stack-monitoring (Stack monitoring)

@ycombinator ycombinator self-assigned this Mar 30, 2020
@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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Feature:Stack Monitoring good first issue Indicates a good issue for first-time contributors libbeat Team:Services (Deprecated) Label for the former Integrations-Services team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants