-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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 libsigar #11034
Comments
+1 in general |
+1 |
the fact that it works without mainly comes for the cases where there isn't an OS sigar supports, or its running embedded and someone doesn't wish to distribute sigar. My main concern with sigar is that the project has stagnated. There hasn't been a new release since 1.6.4 which happened a few years ago... . It has been very handy to use. Single API call to get the status on 100 node cluster. Many monitoring tools (bigdesk, ElasticHQ, ...) for ES rely on it (since its part of the API), and the ones I have found handy are basic ones, just with an opportunity to see the state across the cluster easily. I've mainly used cpu (os and process), swap usage, and in extreme cases network and fs statistics. |
Do I understand this correctly that you are considering dropping REST APIs (cluster, admin...) that expose info based on Sigar lib? This would be unfortunate IMO. Not because I am Bigdesk maintainer but because getting this info directly from ES is extremely valuable feature. It is one of the reasons why we are using ES in our team. |
this is about removing the native library not the stats it's providing. We can in the meanwhile get several of them from other sources. We might not be able to provide a 1 to 1 replacement but a native lib that is basically unmaintained for more than half a decade is not really an option. |
Supposedly ES works if its not available, hence, its unnecessary.
Having uunecessary JNI dependencies is too much.
The text was updated successfully, but these errors were encountered: