It’s called Grafana 
and already used by the Community. It also has some kind of a dashboards online store, so you can share your own dashboard with the Community there or via GitHub.
1 Like
Interesting, I have just checked, Grafana offers a JSON API Grafana Datasource plugin.
It looks like with that you might be able to use the node API as data source instead of running a database.
I wonder if the current dashboard could be replaced with such a solution.
Likely it’s possible, it’s up on the Community. I do not believe that it would be done by Storj any time soon, it’s even not considered.
1 Like
I think there’s a couple dashboards to start with. But you’d probably always want something like Prometheus in there for long-term metrics (instead of Grafana only pulling live data)
1 Like
Useful info this vetted detail. Any idea why this node is not vetted to ap1 after 12 months and all others good?
Hello @Unique,
Welcome back!
What does this script show?
The earnings script shows all the nodes are OK. So the Url and the script are at odds. However I do notice that on this node the earnings for Ap1 are down compared to my other nodes.
There is no any relations between your nodes, except that they share the same IP /24 range of the public IPs and maybe a little difference in performance. But basically they are unique, so the usage pattern may differ a lot.
Your results just confirms that the implementation of the vetting status on the dashboard has a bug, you may subscribe to this issue:
It looks like it has landed and I can see it in the API as it is being rolled out. This is great.
There is another thing when I look at the /api/sno endpoint the satellites are shown with their ID.
In /api/sno/satellites → audits, the satellites are displayed with their names only, which are not neccessarily unique.
Is it possible to have the an ID key in the audit object in /api/sno/satellites → audits for each satellite additional to the name?
I would guess, but I believe it is a call for the Community to suggest a PR.