-
Notifications
You must be signed in to change notification settings - Fork 156
Description
Please make sure that this is a feature request.
System information
- Scylla version (you are using): 2025.1
- Are you willing to contribute it (Yes/No): No
Describe the feature and the current behavior/state.
right now we see number of requests hitting Scylla, but if Scylla doesn't reply with any data (e.g. with bloom filters) we don't see it
we do see cache hits and cache misses, so we can kinda assume the query was refused by bloom filter, but at the same time there are other CQL queries from driver which will skew this assumption, so if we can exactly know how much is served by bloom filters (resp. how effective they are)
we'd like to see how many of requests
Who will benefit with this feature?
scoping, sizing, benchmarking, use case testing
tuning corner cases where they have lots of misses (you can then adjust fp chance based on this)
Any Other info.
I have no clue if Scylla has such metric, most likely not, 2025.3.1 list of metrics with "bloom" in them:
# HELP scylla_database_clustering_filter_count Counts bloom filter invocations.
# HELP scylla_database_clustering_filter_fast_path_count Counts number of times bloom filtering short cut to include all sstables when only one full range was specified.
# HELP scylla_database_clustering_filter_sstables_checked Counts sstables checked after applying the bloom filter. High value indicates that bloom filter is not very efficient.
# HELP scylla_database_clustering_filter_surviving_sstables Counts sstables that survived the clustering key filtering. High value indicates that bloom filter is not very efficient and still have to access a lot of sstables to get data.
# HELP scylla_sstables_bloom_filter_memory_size Bloom filter memory usage in bytes.
# TYPE scylla_sstables_bloom_filter_memory_size gauge
so not sure if above (or any other without bloom in its name) can be used