-
Notifications
You must be signed in to change notification settings - Fork 32
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
gstatus is not compatible with this version of glusterfs 4.1.2 #11
Comments
+1 |
me too :-( ... ok 4.1.5 for me |
@metrax @tkriviradev @Apollon77 gstatus is deprecated not supported on glusterfs 4.x. However, there is some work on better monitoring tools, will keep posted. |
that would be awesome! |
I deleted the version check, some functions work well on version 4.1.5 |
And which? Which not? ;-) do you have more Details? |
@sac If the tool is deprecated, what's the successor? Thank you. |
I did not planned to use Prometeus just to monitor my Gluster installation. SO please provide something more generic like this script. |
I just updated a test cluster from GlusterFS 3.8.8 --> 6.1-1 and because of that lost the gstatus support, which we use for monitoring, but still got it to work;
|
I use it the same with glusterfs 5.6 ... So why not chaning the code in a way that it can be used again officially? |
Sorry for delay. We wanted to keep https://github.com/gluster/gluster-prometheus as a possible next step. We will announce in mailing list when a 'decent' monitoring tool is ready. |
I think it was said in an other thread, but prometheus is not that common beside the enterprise segment (my opinion). i think for many more private or SMB installations this would net really be an option ... that python script is easy and without dependencies to other tech |
Fixed in this bulid: https://copr.fedorainfracloud.org/coprs/sac/gstatus/builds/ should resolve this issue. |
Hi,
please fix this Version compatibility problem.
#gstatus -a -o json gstatus is not compatible with this version of glusterfs 4.1.2
I'm using the latest git version.
Thank you!
The text was updated successfully, but these errors were encountered: