Data Stores Observability Dashboard

Thanks for the suggestion - our team will look into it.

2 Likes

Thanks for the feedback.

Showing request rate per Player Count is an interesting idea. Currently Player Count (CCU) is available on the Performance page, but I agree it would be nicer to have one chart for that information.

We thought about showing the limits but it can be confusing as DataStores request limit are enforced on each game server, therefore it’s possible that an experience still has lots available quota but one server starts to throttle requests.

1 Like

What would be the use case for bandwidth of data per minute ?

1 Like

Could you elaborate? Do you mean to see the keys or the values?

1 Like

Thanks for the feedback. Please see my other comment, and reply here if you have any other comments or suggestions.

We thought about showing the limits but it can be confusing as DataStores request limit are enforced on each game server, therefore it’s possible that an experience still has lots available quota but one server starts to throttle requests.

1 Like

Within this article, it explains that there is a per key limit. If we were able to understand how close we are to this limit for the top used keys in the experience, this would be helpful to understand where to optimise and understand data usage, and perhaps cut down or split across more keys in some edge cases.

6 Likes

I see, that’s a good suggestion. We will discuss this feature internally.

4 Likes

Great feature, I just hope you guys add more information to compare to since it’s the total metrics for all servers meaning you won’t know how close you are to the limits and quotas, e.g. Requests per Minute for GetAsync() is 60 + numPlayers × 10 but we have no way of knowing if we are close to that limit without calculating maximum playercount at that time.

2 Likes

Yes i mean the keys and values

1 Like

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.