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

replica/table.cc: Add metrics per-table-per-node #18645

Closed
wants to merge 1 commit into from

Conversation

amnonh
Copy link
Contributor

@amnonh amnonh commented May 13, 2024

Previous patches add per-table metrics reported per node (instead of per shard). Enabling table view for customers.
The per-node metrics reporting is on by default; this is why the number of metrics is limited.

This patch adds metrics that will be reported per table, per node. The added metrics (that are part of the per-table per-shard metrics) are:
scylla_column_family_cache_hit_rate
scylla_column_family_read_latency
scylla_column_family_write_latency
scylla_column_family_live_disk_space

And they are used by the keyspace/table dashboard.
Fixes #18642
image

No need to backport, it's part of 6.0

This patch adds metrics that will be reported per-table per-node.
The added metrics (that are part of the per-table per-shard metrics)
are:
scylla_column_family_cache_hit_rate
scylla_column_family_read_latency
scylla_column_family_write_latency
scylla_column_family_live_disk_space

Fixes scylladb#18642

Signed-off-by: Amnon Heiman <amnon@scylladb.com>
@amnonh amnonh added the backport/none Backport is not required label May 13, 2024
@scylladb-promoter
Copy link
Contributor

🟢 CI State: SUCCESS

✅ - Build
✅ - Container Test
✅ - dtest
✅ - dtest with topology changes
✅ - Unit Tests

Build Details:

  • Duration: 4 hr 34 min
  • Builder: i-06be5101f20b0dfec (m5ad.12xlarge)

@github-actions github-actions bot added promoted-to-master backport/5.4 Issues that should be backported to 5.4 branch once they'll be fixed labels May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/none Backport is not required backport/5.4 Issues that should be backported to 5.4 branch once they'll be fixed promoted-to-master
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Need to add more metrics to the per-table-per-instance reporting
3 participants