Read count missing in monitoring tools

The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.

Synopsis:

You see a count of zero for reads in asinfo, Aerospike Monitoring Stack, etc.

Root cause:

Reads and batch reads are tracked separately, so if looking for read traffic that is not showing up, it is most likely due to the use of batch reads. This can be confirmed by running :

asinfo -v stats -l|grep batch_index

The Number of reads should show in batch_index_initiate (Cumulative value since service started)

batch_index_initiate=0
batch_index_queue=0:0,0:0,0:0,0:0,0:0,0:0
batch_index_complete=0
batch_index_error=0
batch_index_timeout=0
batch_index_delay=0
batch_index_unused_buffers=0
batch_index_huge_buffers=0
batch_index_created_buffers=0
batch_index_destroyed_buffers=0
batch_index_proto_uncompressed_pct=0.000
batch_index_proto_compression_ratio=1.000

Timestamp

October 2020