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

[Status API] When the instance is running on Windows, the Status API should remove the OS Load fields instead of returning them as 0 #17548

Open
tsullivan opened this issue Apr 4, 2018 · 3 comments
Labels
Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc triage_needed

Comments

@tsullivan
Copy link
Member

Today, if a Kibana instance runs on Windows the status API returns 0 for the OS Load fields. OS Load is not available in the Windows environment, so 0 is misleading. The Status API should just not include these fields at all.

@jbudz jbudz added the Team:Operations Team label for Operations Team label Apr 5, 2018
@tylersmalley
Copy link
Contributor

Is this still an issue with your recent changes in #20577?

@tsullivan
Copy link
Member Author

Is this still an issue with your recent changes in #20577?

That PR doesn't do anything to change the calculation of OS Load, so I think the answer is yes.

@jbudz jbudz added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc and removed Team:Operations Team label for Operations Team labels Sep 15, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc triage_needed
Projects
None yet
Development

No branches or pull requests

5 participants