7.0.0 gauge  Seconds of history the bucket should aim to retain on disk.

7.0.0 gauge  The μs threshold of drift at which we will increment a vbucket's ahead counter.

7.0.0 gauge  The μs threshold of drift at which we will increment a vbucket's behind counter.

7.0.0 gauge  The accumulated number of times the corresponding kv_ep_hlc_drift_count has been updated

7.0.0 gauge / seconds  The accumulated drift between this node's HLC and the remote node. For active vbucket's this represents the difference in CAS and local HLC for withMeta operations, for replica vbucket's this represents the difference in CAS and local HLC from DCP replication.

7.0.0 gauge  The acceptable μs threshold of drift at which we accept a new cas value.

7.1.0 gauge / bytes  The total byte size of all items, no matter the vbucket's state, no matter if an item's value is ejected. Tracks the same value as ep_total_cache_size

7.0.0 gauge 

7.0.0 gauge  Interval in seconds to wait between HashtableResizerTask executions.

7.0.0 gauge  The initial and minimum number of slots in HashTable objects.

7.0.0 gauge  Delay in seconds before decreasing the size of a HashTable following a previous resize.

7.0.0 gauge 

7.0.0 gauge  Accumulated count of read system calls issued by BG fetches, only maintained by couchstore buckets

7.0.0 gauge / bytes  Total number of bytes read during compaction

7.0.0 gauge / bytes  Total number of bytes written during compaction

7.0.0 gauge / bytes  Total number of bytes written. Only maintained by couchstore buckets and includes Couchstore B-Tree and other overheads

7.0.0 gauge / bytes  Total number of bytes read

7.0.0 gauge / bytes  Total number of bytes written

7.0.0 gauge  Number of times a transaction failed to start due to storage errors

7.0.0 gauge  Number of times a transaction failed to commit due to storage errors

7.0.0 gauge  Maximum time (in ms) item compression task will run for before being paused (and resumed at the next item_compressor_interval).

7.0.0 gauge  How often the item compressor task should run (in milliseconds)

7.0.0 gauge  Number of items compressed by the item compressor task.

7.0.0 gauge  Number of items visited (considered for compression) by the item compressor task.

7.0.0 gauge  The age percentage used when determining the age threshold in the learning_age_and_mfu eviction policy.

7.0.0 gauge 

7.0.0 gauge  Percentile of existing item MFU distribution to use to determine the MFU to give to new items (0 would insert new items with MFU equal to that of the coldest item present; 100 to that of hottest item present) for the upfront_mfu_only eviction strategy.

7.0.0 gauge  Time between updates of the initial MFU given to new items (seconds)

7.0.0 gauge  Number of times an item is not flushed due to the expiry of the item

7.0.0 gauge  Number of times an item failed to flush due to storage errors

7.0.0 gauge  Maximum time (in ms) itemFreqDecayer task will run for before being paused.

7.0.0 gauge  The percent that the frequency counter of a document is decayed when visited by item_freq_decayer.

7.0.0 gauge  The number of item objects allocated

7.6.0 counter  The number of item object allocations

7.6.0 counter  The number of item object deallocations

7.0.0 counter  Number of items expelled from checkpoints. Expelled refers to items that have been ejected from memory but are still considered to be part of the checkpoint.

7.0.0 counter  Number of items removed from closed unreferenced checkpoints

7.0.0 gauge / bytes  Memory used to store items metadata, keys and values in the system, no matter the vbucket's state

7.2.0 gauge / bytes  Compressed disk size of latest version of the LSM Trees. This includes history

7.1.0 gauge  Number of block cache hits

7.1.0 gauge / bytes  Memory used by block cache. Accounts for allocated size of blocks that includes allocator internal fragmentation and any internal cache overheads due to auxilliary structures

7.1.0 gauge  Number of block cache misses

7.0.0 gauge  Magma maintains a bloom filter per sstable in the LSMTree. The bloom filters are used to reduce IO in case of non-existent This config sets the accuracy of the bloom filters ie. (1 - accuracy) = false positive rate

7.0.0 gauge  The bloom filters at the bottom level are used to avoid IO in case of non-existent keys. Also most of the data resides in the bottom level. This config allows for lowering of bloom filter accuracy of sstables residing in the lowermost level of the LSMTree.

7.1.0 gauge / bytes  Bloom filter memory usage in all versions of the LSM Trees

7.1.0 gauge / bytes  Memory usage for some buffers

7.1.0 gauge / bytes  Data written to key, seq, local index as part of the KV frontend writes.

7.1.0 gauge / bytes  Total bytes returned via get (excluding bytes returned from sequence iterator)

7.1.0 gauge / ratio  Bytes read by get / number of Gets

7.2.0 gauge / bytes  Checkpoint overhead

7.0.0 gauge  Frequency of checkpoint interval; in seconds. A checkpoint provides a rollback point to which the data store can rollback to in the event of a failure.

7.0.0 gauge  Threshold of data written before a checkpoint is created; threshold is based on a fraction of the total data size. Checkpoints require data to be retained in order to provide rollback capability. If the amount of data written during a checkpoint interval is large, we need to do more frequent checkpoints to reduce space amplification.

7.1.0 gauge  Count of Magma compactions in key, seq and local index.

7.2.0 gauge  Data blocks compressed size; actual size in storage

7.2.0 gauge / ratio  The compression ratio calculated by dividing the uncompressed data size by the compressed data size

7.2.0 gauge / ratio  Estimated percentage of space savings in compressed data blocks (0-100)

7.2.0 gauge  Data blocks uncompressed size

7.0.0 gauge  Magma compaction always removes duplicate keys but not all sstables are visited during compaction.. This is the minimum fragmentation ratio threshold for when a compaction will be triggerred.

7.0.0 gauge  Magma uses a lazy update model to maintain the sequence index. It maintains a list of deleted seq #s that were deleted from the key Index.

8.0.0 gauge  Count of Magma compactions issued to drop older encryption keys.

7.0.0 gauge  The block cache is an LRU policy driven cache that is used to maintain index blocks for the sstable's btrees.

7.0.0 gauge  Using direct IO tells magma to bypass the file system cache when writing or reading sstables.

7.0.0 gauge  Group Commit allows transactions in magma to be grouped together to reduce the number of WAL fsyncs. When a transaction is ready to fsync, if there are new transactions waiting to start, we stall the transaction waiting to fsync until there are no more transactions waiting to start for a given magma instance.

7.0.0 gauge  When enabled, if copying a write batch into memtable results in exceeding the write cache quota, Magma avoids the copy and instead flushes the batch to disk on the writer thread itself. This tradeoffs an increase in write latency for reduced memory consumption and obeys quota limits. If copying a batch keeps us under the quota, Magma will to continue to copy and do the flush in background.

7.0.0 gauge  When true, the kv_engine will utilize Magma's upsert capabiltiy but accurate document counts for the data store or collections can not be maintained.

7.0.0 gauge  WAL ensures Magma's atomicity, durability. Disabling it is useful in performance analysis.

7.0.0 gauge  All compactions perform expiry but not all sstables are visited by compaction. Magma maintains an expiry histogram across the kvstore to help determine which range of sstables need to have compaction run on them because there are a significant number of expired items. The frag threshold is the number of expired keys vs keys in the data store.

7.0.0 gauge  Magma maintains statistics about expired documents to run compaction based on magma_expiry_frag_threshold. This config determines the the expiry purger polling interval in seconds to trigger compaction on eligible sstables

7.1.0 gauge  Number of compactions triggered by file count

7.0.0 gauge  Percentage of storage threads that are flusher threads (i.e. with a value of 20 we will allocate 4 (1/5th) of the storage threads to flushers and the remaining 16 (4/5ths) threads will be compactors).

7.1.0 gauge  Number of write cache flushes performed

7.0.0 gauge  The percentage of fragmentation a magma bucket aims to maintain. A 100 value will disable sequence tree compactions by setting the desired fragmentation percentage to 100%. Smaller compactions of the key and local indexes will still run.

7.1.0 gauge / ratio  Fragmentation on disk (excludes history)

7.0.0 gauge  The interval at which FusionFS should create a log checkpoint on the FusionMetadataStore and delete eligible logs from the FusionLogStore, in seconds.

7.0.0 gauge  The threshold at which the fusion log store will perform garbage collection. This is a ratio between 0.0 and 1.0.

7.0.0 gauge  The interval between kvstore syncs to fusion, in seconds.

7.1.0 gauge  Number of get operations

7.0.0 gauge  When a transaction is about to stall because there are pending transactions waiting to start, if there already are transactions waiting and the oldest transaction has been waiting for magma_group_commit_max_sync_wait_duration ms or more, the current transaction will perform the fsync. When group commit is enabled and both magma_group_commit_max_sync_wait_duration and magma_group_commit_max_transaction_count are set to 0, transactions will stall until there are no more transactions waiting to start. Unit is milliseconds.

7.0.0 gauge  When a transaction is about to stall because there are pending transactions waiting to start, if there already are magma_group_commit_max_transaction_count including the current transaction waiting, the current transaction will perform the fsync. When group commit is enabled and both magma_group_commit_max_sync_wait_duration and magma_group_commit_max_transaction_count are set to 0, transactions will stall until there are no more transactions waiting to start.

7.0.0 gauge  Frequency of heartbeat interval; in seconds. A heartbeat task is scheduled to provide cleanup and maintenance when magma is idle.

7.1.0 gauge / bytes  Memory usage for MagmaHistogramStats and file histograms

7.2.0 gauge / bytes  The logical data size of history

7.2.0 gauge / bytes  The logical disk size of history

7.2.0 gauge / bytes  History eviction bytes based on size

7.2.0 gauge / bytes  History eviction bytes based on time

7.1.0 gauge / ratio  Proportion of keyIndex (data+index blocks) and seqIndex (index blocks) in memory

7.0.0 gauge  The WAL buffer is used to stage items to the write ahead log along with control information like begin and end transaction. This parameter refers to the initial WAL buffer size. The WAL buffer will adjust its size up to a maximum of 4MB or down to a minimum of 64KB depending on the transaction batch size with consideration for other magma components which consume memory such as the block cache, bloom filters, write cache and meta data overhead.

7.1.0 gauge  Number of DocInsert operations

7.0.0 gauge  Magma uses SSTables for storage. SSTables are made up of different types of blocks. Data blocks contain the bulk of the data and contain the key and metadata for each of the items in the block. Larger block sizes can decrease storage space by better block compression but they require more memory, cpu and io bandwidth to read and write them.

7.0.0 gauge  Magma uses SSTables for storage. SSTables are made up of different types of blocks. Index blocks contain keys that help traverse the SSTable to locate the data item. Larger block sizes can decrease storage space by better block compression but they require more memory, cpu and io bandwidth to read and write them.

7.2.0 gauge  Number of compactions triggered by file count for the KeyIndex

7.2.0 gauge  Number of compaction performed on the writer thread for the KeyIndex

7.1.0 gauge / bytes  The logical data size, including history

7.1.0 gauge / bytes  The logical disk size, including history

7.1.0 gauge / bytes  Memory used by LSMTree objects

7.0.0 gauge  Maximum # of checkpoints retained for rollback.

7.0.0 gauge  If the number of storage threads = 0, then we set the number of storage threads to this value and use magma_flusher_thread_percentage to determine the ratio of flusher and compactor threads.

7.0.0 gauge  Maximum time (in seconds) that data is kept in level 0 before it is merged.

7.0.0 gauge  Maximum amount of data that is replayed from the WAL during magma recovery. When this threshold is reached magma, creates a temporary checkpoint to recover at. This is per kvstore and in bytes.

7.0.0 gauge  Magma uses a common skiplist to buffer all items at the shard level called the write cache. The write cache contains items from all the kvstores that are part of the shard and when it is flushed, each kvstore will receive a few items each. Regardless of how much memory might be available, this would be the maximum amount that could be allocated.

7.0.0 gauge  Fraction of memory quota used by magma as it's low water mark. Magma uses this low watermark to size it's write cache and block cache. This sizing includes bloom filters memory usage but bloom filter eviction is based on the memory quota

7.0.0 gauge  Magma total memory ratio of the Bucket Quota across all shards and Magma limit's it's memory usage to this value.

7.0.0 gauge  Minimum interval between two checkpoints; in seconds. Prevents excessive creation of checkpoints.

7.0.0 gauge  Magma creates value blocks for values larger than this size. Value blocks only contain a single KV item and their reads/writes are optimised for lesser memory consumption as it avoids many value copies. For example, magma block compression is turned off for them as compression requires an output buffer as large as the input buffer. This is fine since for such large docs, per document Snappy compression already should give good enough space savings. This setting should be >= SeqIndex data block size or else it won't take effect.

7.0.0 gauge  Apply Snappy compression to each document when persisted (magma only)

7.1.0 gauge / bytes  Memory consumed by read ahead buffers. They are used for compactions and sequence iterators. This is included in BufferMemUsed

7.1.0 gauge / bytes  Total bytes read from disk as per Magma's manual accounting in various code paths

7.1.0 gauge / bytes  Total bytes read from disk by compactors

7.1.0 gauge / bytes  Total bytes read from disk by gets

7.1.0 gauge / ratio  Bytes Read from disk by only Get threads / Bytes outgoing

7.1.0 gauge / ratio  Bytes read from disk / bytes outgoing. Bytes read from disk includes Gets and compactors (excluding WAL)

7.1.0 gauge  Number of read IOs performed

7.1.0 gauge / ratio  Number of read IOs performed by GetDocs divided by the number of GetDocs

7.0.0 gauge  Magma uses SSTables for storage. SSTables are made up of different types of blocks. Data blocks contain the bulk of the data and contain the key, metadata and value for each of the items in the block. Larger block sizes can decrease storage space by better block compression but they require more memory, cpu and io bandwidth to read and write them. If this is less than magma_min_value_block_size_threshold, Magma will internally auto configure the value block size to be as large as this.

7.0.0 gauge  Magma uses SSTables for storage. SSTables are made up of different types of blocks. Index blocks contain keys that help traverse the SSTable to locate the data item. Larger block sizes can decrease storage space by better block compression but they require more memory, cpu and io bandwidth to read and write them.

7.6.0 gauge  Count of Magma compactions in seq index that compact the data level. This are already accounted in ep_magma_seqindex_compactions hence not part of the magma_compactions Prometheus stat family.

7.6.0 gauge / bytes  Data written to seq index delta levels as part of frontend update operations. This is already accounted in ep_magma_seqindex_bytes_incoming hence not part of Prometheus stat family magma_bytes_incoming.

7.6.0 gauge / bytes  Bytes written by Magma flushes, compactions of the seq index delta levels. This is already accounted into ep_magma_sequndex_write_bytes hence not part of the Prometheus stat family magma_write_bytes.

7.2.0 gauge  Number of compactions triggered by file count for the SeqIndex

7.2.0 gauge  Number of compaction performed on the writer thread for the SeqIndex

7.1.0 gauge  Number of set operations (DocUpsert)

7.0.0 gauge  Couchstore generates a commit point at the end of every batch of items. During normal operation, Magma checkpoints are taken at every magma_checkpoint_interval. Many of the tests require more frequent checkpoints so this configuration parameter makes sure every batch generates a checkpoint. Each checkpoint generated in this way is a "Sync" checkpoint and isn't going to be useful for rollback as it only the latest checkpoint is a "Sync" checkpoiont. A "Rollback" checkpoint will be made instead if we set magma_checkpoint_interval to 0. The "Rollback" checkpoints are stored in the checkpoint queue as potential rollback points. Should be used for testing only!

7.1.0 gauge  Number of fsyncs performed

7.1.0 gauge / bytes  Memory used by sstable metadata

7.1.0 gauge / bytes  Memory used by SSTable objects

7.1.0 gauge  Number of files used for tables

7.1.0 gauge  Number of table files created

7.1.0 gauge  Number of table files deleted

7.1.0 gauge / bytes  Compressed size of all SSTables in all checkpoints, WAL and any other files on disk

7.1.0 gauge / bytes  Total memory used by bloom filters, write cache, block cache and index blocks This account for all versions of the trees

7.6.0 gauge / bytes  Memory consumed by all LSMTree TreeSnapshots

7.1.0 gauge  Number of time-to-live based compactions

7.1.0 gauge / bytes  Disk usage by the WAL

7.1.0 gauge / bytes  Total WAL memory used, including WAL buffer and any auxiliary memory

7.1.0 gauge / bytes  Bytes written by Magma flushes, compactions and WAL writes.

7.1.0 gauge / bytes  Bytes written by Magma compactions.

7.1.0 gauge / bytes  Memory usage of the write cache

7.0.0 gauge  Memory is maintained across 3 magma components; Bloom filters, Block cache and Write cache. The least important of these is the write cache. If there is insufficent memory for the write cache, the write cache will grow to the size of the batch and then be immediately flushed and freed. If there is available memory, the write cache is limited to 20% of the available memory (after bloom filter and block cache get their memory up to magma_max_write_cache (128MB). Bloom filters are the most important and are never paged out. Bloom filter memory can cause magma to go above the memory quota. To allevaite this, the bottom layer where the majority of bloom filter memory is, won't use bloom filters when OptimizeBloomFilterForMisses is on (which it is by default). The block cache grows each time the index sizes change. But its growth is bounded by the available memory or what's left over after the bloom filter memory is subtracted.

7.1.0 gauge  Number of compaction performed on the writer thread

7.0.0 gauge  The expected max number of checkpoints in each VBucket on a balanced system. Note: That is not a hard limit on the single vbucket. That is used (together with checkpoint_memory_ratio) for computing checkpoint_max_size, which triggers checkpoint creation.

7.0.0 gauge  maximum number of failover log entries

7.0.0 gauge  Maximum number of bytes allowed for 'privileged' (system) data for an item in addition to the max_item_size bytes

7.0.0 gauge  Maximum number of bytes allowed for an item

7.0.0 gauge  Maximum number of bg fetcher objects (the number of concurrent bg fetch tasks we can run). 0 = auto-configure which means we use the same number as the number of reader threads (num_reader_threads).

7.0.0 gauge  Maximum number of flusher objects (the number of concurrent flusher tasks we can run). 0 = auto-configure which means we use the same number as the number of shards (max_num_shards - for historic reasons). See also num_writer_threads.

7.0.0 gauge  Maximum mumber of shards (0 = auto-configure)

7.0.0 gauge  Bucket Priority relative to other buckets

7.0.0 gauge  Memory quota (in bytes) for this bucket.

7.0.0 gauge  Maximum number of threads of any single class (0 = automatically select based on core count)

7.0.0 gauge  A maximum TTL (in seconds) that will apply to all new documents, documents set with no TTL will be given this value. A value of 0 means this is disabled

7.0.0 gauge  Maximum number of vbuckets expected

7.1.0 gauge / bytes  Memory recovered from Checkpoint by expelling clean items (i.e. items processed by all cursors) from the queue

7.1.0 gauge / bytes  Amount of memory freed through ckpt removal

7.0.0 gauge  The bucket's memory used high watermark.

7.0.0 gauge  Ratio of the Bucket Quota at which to place the high watermark. This is the maximum desired memory usage. This value should be lower than mutation_mem_ratio to avoid no memory errors.

7.0.0 gauge  The bucket's memory used low watermark.

7.0.0 gauge  Ratio of the Bucket Quota at which to place the low watermark. This is the point to which to reduce the memory usage of the bucket after hitting the high watermark.

7.0.0 gauge  True if memory usage tracker is enabled

7.0.0 gauge  What percent of max_data size should we allow the estimated total memory to lag by (EPStats::getEstimatedTotalMemoryUsed)

7.0.0 gauge / bytes  Estimate of how much metadata has been written to disk since startup

7.0.0 gauge / bytes  Total memory used by meta data, including the key

7.0.0 gauge  specifies a minimum compression ratio below which storing the document will be stored as uncompressed.

7.0.0 gauge  Ratio of the Bucket Quota that can be used before mutations return tmpOOMs

7.0.0 gauge  Controls which error code should be returned when attempting to unlock an item that is not locked. When value is true, the legacy temporary_failure is used instead of not_locked.

7.0.0 gauge  Number of times we ran accesss scanner to snapshot working set

7.0.0 gauge  Number of times accesss scanner task decided not to generate access log

8.0.0 counter  The total number of CAS value regenerated

7.1.0 gauge  The number of checkpoint objects allocated

7.6.0 counter  The number of checkpoint object allocations

7.6.0 counter  The number of checkpoint object deallocations

7.6.0 gauge  Number of checkpoints detached from CM and owned by Destroyers

7.0.0 counter  Number of items that could not be ejected

7.0.0 counter  Number of times we ran expiry pager loops to purge expired items from memory/disk

7.0.0 counter  Number of times we ran the freq decayer task because a frequency counter has become saturated

8.0.0 counter  The total number of invalid CAS values.

7.0.0 gauge  The number of non-resident items

7.0.0 counter  Number of times Not My VBucket exception happened during runtime

7.0.0 counter  Number of times we ran pager loops to seek additional memory

7.0.0 counter  Number of times item values got ejected from memory to disk

7.0.0 gauge  Global number of shared worker threads

7.0.0 gauge  Number of times unrecoverable OOMs happened while processing operations

7.0.0 gauge  How long in milliseconds the ItemPager will sleep for when not being requested to run

7.0.0 gauge  Expected number of times the PagingVisitor will check the pause condition per vBucket

7.0.0 gauge  For persistent buckets, the count of compaction tasks.

8.0.0 gauge / seconds  The longest time spent in a disk operation that is currently executing

7.0.0 gauge  Number of ops awaiting pending vbuckets

7.0.0 gauge  Max ops seen awaiting 1 pending vbucket

7.0.0 gauge / seconds  Max time (µs) used waiting on pending vbuckets

7.0.0 counter  Total blocked pending ops since reset

7.0.0 gauge  Total VB persist state to disk

7.0.0 gauge  Age in seconds after which tombstones may be purged. Defaults to 3 days. Max of 60 days. If this is dynamically changed for a magma bucket then magma may not trigger compactions when it should, this can be avoided by running a full manual compaction after changing this parameter.

7.0.0 gauge  Mark primary warm-up as complete when the number of values loaded by warm-up reaches this percentage of the available values. This is checked after evaluating primry_warmup_min_memory_threshold.

7.0.0 gauge  Mark primary warm-up as complete when bucket memory usage reaches this percentage of max_data_size. This is checked before evaluating primry_warmup_min_items_threshold.

7.0.0 gauge  Number of items queued for storage

7.0.0 gauge  The ratio for calculating how many RangeScans can exist, a ratio of total KVStore scans.

7.0.0 gauge  The maximum number of range scan tasks that can exist concurrently. Setting to 0 results in num_auxio_threads - 1 tasks

7.0.0 gauge  The maximum lifetime in seconds for a range-scan. Scans that don't complete before this limit are cancelled

7.0.0 gauge  The size of a buffer used to store data read during the I/O phase of a range-scan-continue. Once the buffer size is >= to this value the data is sent to the connection

7.0.0 gauge  whether erroneous tombstones need to be retain during compaction. Erroneous tombstones are those that have invalid meta data in it. For example, a delete time of 0.

7.0.0 gauge  Number of rollbacks on consumer

8.0.0 counter  To facilitate warm-up progress tracking this value represents how many values need to be loaded to reach 100% of values loaded. This counter is only initialised when warm-up reaches the "loading access log", "loading k/v pairs" or "loading data" state and the ratio of ep_warmup_value_count and this provides insight into progress.

7.0.0 gauge  Stop secondary warm-up when the number of values loaded by warm-up reaches this percentage of the available values. This is checked after evaluating secondary_warmup_min_memory_threshold.

7.0.0 gauge  Stop secondary warm-up when bucket memory usage reaches this percentage of max_data_size. This is checked before evaluating secondary_warmup_min_items_threshold.

7.0.0 gauge  Timeout in seconds after which a pending SeqnoPersistence operation is temp-failed

8.0.0 gauge / bytes  The number of bytes read when copying/downloading snapshots

7.0.0 gauge / seconds  System-generated engine startup time

7.0.0 gauge  The number of storedval objects allocated

7.6.0 counter  The number of storedval object allocations

7.6.0 counter  The number of blob object deallocations

7.6.0 counter / bytes  The total number of bytes ever allocated for storedval objects

7.6.0 counter / bytes  The total number of bytes ever freed by deallocated storedval objects

7.0.0 gauge  The maximum number of supported replicas for SyncWrites. Attempts to issue SyncWrites against a topology with more replicas than this setting will fail with DurabilityImpossible.

7.0.0 counter  Number of times temporary OOMs happened while processing operations

7.0.0 gauge / bytes  The total byte size of all items, no matter the vbucket's state, no matter if an item's value is ejected. Tracks the same value as ep_ht_item_memory

7.0.0 gauge  Total number of items de-duplicated when queued to CheckpointManager

7.2.0 gauge  Total number of items de-duplicated when flushed to disk

7.0.0 gauge  Total number of persisted deletions

7.0.0 gauge  Total number of items queued for persistence

7.0.0 gauge  Total number of persisted new items

7.0.0 gauge  Total number of items persisted

7.0.0 gauge  The amount of items that have not been written to disk

7.6.0 counter / bytes  The total number of bytes ever allocated for blob objects

7.6.0 counter / bytes  The total number of bytes ever freed by deallocated blob objects

7.0.0 gauge  Total vBuckets (count)

7.0.0 gauge  Number of vbucket deletion events

7.0.0 gauge / seconds  Avg wall time (µs) spent by deleting a vbucket

7.0.0 gauge  Number of failed vbucket deletion events

7.0.0 gauge / seconds  Max wall time (µs) spent by deleting a vbucket

7.0.0 gauge  Are vBucket mappings (key -> vBucket) checked by the server? This is a sanity checking mode which crc32 hashes the key to ensure that the client is supplying the expected vBucket for each key.

7.0.0 gauge  Is Warmup of existing data enabled

7.0.0 gauge  AccessLog loading operates in batches of this size (dictates the max number of keys issued to the KVStore::getMulti function)

7.0.0 gauge  The duration (in ms) after which warmup's LoadAccessLog phase will yield and re-schedule; allowing other tasks on the same thread pool to run.

7.0.0 gauge  The duration (in ms) after which warmup's backfill scans will yield and re-schedule; allowing other tasks on the same threads to run.

7.0.0 gauge  Ratio controlling how many tasks that will be created in the KeyDump, LoadingKVPairs and LoadingData phases. This is a ratio using the number of shards as the denominator and least 1 task will be created per phase. A value of 0.0 will create tasks equal to the lower of #shards or #reader-threads, a value of 1.0 restores the orginal behaviour, 1 task per shard.

7.0.0 gauge  Duplicates encountered during warmup

7.1.0 counter  To facilitate warm-up progress tracking this value represents how many keys need to be loaded to reach 100% keys loaded. This count is useful for progress tracking for Value Eviction buckets during the "loading keys" state and the ratio of ep_warmup_key_count and this provides insight into progress. This value is the same for the estimated number of keys required to be loaded for secondary warmup, if secondary warmup is enabled.

7.1.0 counter  To facilitate warm-up progress tracking this value represents how many values need to be loaded to reach 100% of values loaded. This counter is only initialised when warm-up reaches the "loading access log", "loading k/v pairs" or "loading data" state and the ratio of ep_warmup_value_count and this provides insight into progress.

7.1.0 counter  Number of keys warmed up

7.0.0 gauge  OOMs encountered during warmup

7.2.0 gauge  The current status of the warmup thread

7.0.0 gauge / seconds  Time (µs) spent by warming data during Primary warm-up

7.1.0 counter  Number of values warmed up

7.0.0 gauge 

7.0.0 gauge 

8.0.0 gauge / bytes  The rate limit for fusion extent migration, in bytes per second.

8.0.0 gauge / bytes  The rate limit for fusion sync uploads, in bytes per second.