[Experimental] Grafana Dashboard for Veeam ONE v11

[jorgedlcruz]

Hi guys,
With Veeam ONE v11, so many new things came into the product. Among others, one of my favorites is the RESTFul API, which will make our life easier when managing licenses on Veeam ONE, link to the official documentation.

But another small detail is that the whole Web Client now uses the same logic as other Veeam products, like VBA, VAO, etc. This means they are built using an "internal" RESTful API, so I've decided to give it a spin, and of course, use just GET methods.

This is truly experimental, it might change, and it is not officially supported. But, still, if you like to take a look, here is the result:

• The how-to in English - https://jorgedelacruz.uk/2021/03/01/loo ... erimental/
• The how-to in Spanish - https://www.jorgedelacruz.es/2021/03/01 ... erimental/

The incredible slick visibility of the last 7 days Jobs:


This is perfect in case you have a few VONE Servers as well, as you will be able to monitor them all under one single Dashboard.

Feedback and ideas are welcome.

[l.scotti]

Great job Jorge.
I'll try next week.

[wishr]

Hi Ludovic,

Please be aware, that currently some of the functions of the Grafana Dashboard for VONE may not work for VONE installations upgraded to v11 from the previous versions but should work for new "clean" v11 deployments.

Thanks

[jorgedlcruz]

Hello,
I have added a new logic to search by the VBR Dashboard, which is the one at the moment I am monitoring with Grafana, it should now look for whatever ID it has, same for widgets and data sources, so grab the last copy to be sure
https://github.com/VeeamHub/grafana/tre ... ne-grafana

Thanks!

[mtellier]

Thanks for sharing, this looks Awesome!

[mtellier]

Thank you very much for sharing, this looks fantastic!

You inspired me to dig into the API using PowerShell, I have shared my learnings in this post.
Veeam ONE RESTFul Tutorial with PowerShell

[wishr]

Hi Mark,

Thanks for sharing! A good example of how flexible and useful can be REST APIs.

We have a lot of plans on expanding our official REST API coverage and I'm really excited the community has already started digging even in the part of the API that is not officially supported.

Thanks