-
Notifications
You must be signed in to change notification settings - Fork 109
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 row count metric for each table #505
Comments
Now that we have metrics for inserted and deleted rows
This metric can be derived as the difference between the two. |
Actually it would be better for this to be its own metric (gauge) because |
joshua-spacetime
added a commit
that referenced
this issue
Nov 3, 2023
joshua-spacetime
added a commit
that referenced
this issue
Nov 3, 2023
4 tasks
joshua-spacetime
added a commit
that referenced
this issue
Nov 4, 2023
joshua-spacetime
added a commit
that referenced
this issue
Nov 6, 2023
joshua-spacetime
added a commit
that referenced
this issue
Nov 6, 2023
joshua-spacetime
added a commit
that referenced
this issue
Nov 6, 2023
joshua-spacetime
added a commit
that referenced
this issue
Nov 6, 2023
joshua-spacetime
added a commit
that referenced
this issue
Nov 6, 2023
kulakowski
pushed a commit
that referenced
this issue
Nov 7, 2023
kulakowski
pushed a commit
that referenced
this issue
Nov 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @kurtismullins:
There are currently metrics around the time it takes to do various operations to tables. To shine a little context on these operations, lets expose a metric which simply states how many rows a given table has.
If this already exists, feel free to just let me know and close this issue. I couldn't find it but may have missed it. An example metric which would be more useful if we knew the row count is:
spacetime_rdb_iter_time_count
.The text was updated successfully, but these errors were encountered: