-
Notifications
You must be signed in to change notification settings - Fork 473
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
Parse xbtop/Record FPGA usage #7570
Comments
Hi @phip123, We have a script compatible with Nagios queries. The output of the nagios script is JSON plus some Nagios flavor text. Running If using Nagios is out of the question you can invoke
Is this what you are looking for? We are always looking on ways to improve! |
Hi, thanks for the comment. Sadly, I'm going to stick with Prometheus and I'm currently working on an exporter that uses xbutil2. I'm using the xbutil command you suggested - is there any way to direct the JSON output to stdout instead of a file? Thanks! |
Hi @phip123, No worries. Thanks for mentioning Prometheus, looks interesting. Unfortunately we cannot. The Nagios plugin functions by creating a temporary file and then deleting it. We can get very close by running |
Hi @dbenusov-xilinx, then I'm following the same approach as Nagios, by creating and deleting a temporary file. Another, somewhat related question, is it possible that the xbutil command locks some resources? For example on instances with multiple FPGAs installed it seems there is some locking going on and even executing the xbutil command in parallel takes longer than individually. |
Hi @phip123 |
I had some time to finally talk to the team about adding the silence feature and it seems like it is more trouble that it is worth considering the uses. If you really need that feature, please open another issue and I will push it further. Thank you for your feedback! |
Hi,
is there any tool/library that provides the output of xbtop in a machine readable format?
I sadly have troubles with the "build with docker" script, otherwise I would simply change the source code.
I figure there must be some sort of monitoring support that is cloud-native (or similar).
Thanks!
The text was updated successfully, but these errors were encountered: