Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add somewhere the meaning of each metric we scrap #86

Open
1 task done
kjlhgfds opened this issue Feb 13, 2023 · 0 comments
Open
1 task done

Add somewhere the meaning of each metric we scrap #86

kjlhgfds opened this issue Feb 13, 2023 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@kjlhgfds
Copy link

Is there an existing feature request for this?

  • I have searched the existing issues before opening this feature request.

Describe the feature you would like to see.

It would be nice to know what each metric we scrap means (ex: MSPT = MilliSeconds Per Tick), maybe even a little bit more elaborated with more in depth meaning and what to expect as value :
It's the amount of time a tick takes to process. If it's higher than 50, the game cannot process 20 ticks in a second and things start to slow down.

How would you like to see this implemented?

It all could be in the README, in the wiki, on the Grafana dashboard (tool tip, etc) or anywhere.

Additional information to this request.

No response

@kjlhgfds kjlhgfds added the enhancement New feature or request label Feb 13, 2023
@Cubxity Cubxity added the documentation Improvements or additions to documentation label Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants