This graph usually makes sense but isn’t doing so this month, especially when combined with the donut on the right.
Anyone else seeing similar behaviour?
v1.116.7
Usually it’s just the satellite botching stat-genertion for a couple days (like the first dip you see for Dec 9/10). I bet it gets fixed soon. Payouts will still be accurate.
3 Likes
I would ignore all of that. Some of the data displayed depends on consistency of local databases (that are almost guaranteed to get corrupted with the recommended use (over Docker mount), some data is reported by satellites and can be missing; graphs don’t show missing data correctly.
Nothing is correct about these graphs in the dashboard. I would completely ignore them. If node starts and port is available - it’s all good.
3 Likes
Thanks both. Wasn’t particularly worried, just curious.
1 Like
All my 17 nodes have the Batman in the dashboard.
Maybe has something to do with the migration to another database that Alexey talked about?
2 Likes
No, this is a usual gap problem because the node’s code treating NULLs as 0, instead of ignoring and do not counting this day.
See
Should be a small change in that code then. Why not just fixing it instead of explaining again and again?
2 Likes
Because it’s not the only thing that is wrong :). If you start fixing this you also have to fix everything else around that area — I’d venture to guess, up to and including completely rewriting data visualizations (I posted a list of other things wrong with it earlier). And therefore wasting time fixing this one bug in existing code that is going to be replaced anyway is not worth it. And on the other hand, the issue is so low on priority list that allocating resources for it is also not a good idea. As a a result, Alexey suffers…
So Batman will live forever! 
1 Like