Possible bug with user ping graph - No data available about plan HOT 8 CLOSED

Aha I see, there's so much data that it expects it in [timestamp, y] format rather than {x: timestamp, y} format that it's currently being fed. Should be an easy fix

from plan.

There's going to be a build with a fix here in ~10 minutes https://github.com/plan-player-analytics/Plan/actions/runs/8160981921

from plan.

Could you check response for /v1/player request in Dev Tools Network tab (Ctrl+Shift+I), click the refresh icon (Next to the time the data was updated) on the player page after opening dev tools

You can right click the request to copy response body and send it here - there should be some ping data there to verify what's wrong

from plan.

I hope that's what you are looking for 🤣

I didn't find any reference for a /v1/player in the network tab, just player?player=UUID

As there is the ping data in there, I think that's the good output :)

Full output in the attached file (can't paste it in here : "There was a problem saving your comment. Your comment is too long (maximum is 65536 characters). Please try again.")
player-Response.txt

A little count on the table "ping" give me 1192, which is the number shown in the response tab, so... might be just an issue with the graph rendering.

from plan.

Look what I just saw in the "console" part :

Lead to : https://assets.highcharts.com/errors/12/

Going to another user stats page, this error is not displayed (I have to fully refresh the page (simple F5) to get this back in the console when this "data bug" occur).

from plan.

Nice, happy to help enhanced this plugin by reporting the bugs I found :')

And yeah, I keep the last 31 Days (in the servers configs), so this could be a big DATA hole :D
I don't think I miss it, but there is no "refresh query rate" for the ping (just an initial delay before starting to gather the data) ?

I've enought storage space for this, just wondering :)

from plan.

Yeah that could be a good addition in the future (feel free to open a suggestion ticket). Currently the ping task timer is hardcoded to run every 2 seconds with a configurable start delay after player joins, and then it stores one value for 30 in-memory values, so one datapoint per minute.

from plan.

Works flawlessly, perfect !

(Now, I just wait on the "FastLogin" plugin integration fix and that'll be all for the bug discovered so far ahah :D )

from plan.