-
Notifications
You must be signed in to change notification settings - Fork 51
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
Where to install Lustre_exporter #152
Comments
Hi, yes, the exporter needs to be run on the servers. Well, it collects metrics that are related to client produced "traffic", but it cannot identify the clients itself. What we do is to identify the IO throughput which comes from the connection with the clients, You welcome! Best |
Thanks for the response and info, Gabriele. I notice that you have forked the H-P lustre exporter to your own. Can you tell me what is different about yours vs. the H-P one listed by Prometheus (though not as an official exporter)? best, |
Hi Greg, up to now we got mainly:
You can get an overview by checking the closed issues of the project here. For more detailed information check the commits after the last commit after the HP fork. Best |
If you are interested, it would be very nice that you contact a Prometheus forum to add your fork to the https://github.com/prometheus-community repository. I guess, you will need an approval from [email protected] too. |
I am not a dev, so please forgive if this suggestion does not make sense. But instead of a second Lustre_exporter, may I suggest merging @gabrieleiannetti enhancements to this Lustre_exporter? Thus making for one, stronger, exporter. Thx |
Hi, this is more a question than an issue. Where is the best place to install the exporter -- on the lustre server(s) or the lustre clients? If I put it only on the servers, will it also collect client traffic metrics? Thanks.
The text was updated successfully, but these errors were encountered: