---
title: "Key metrics to monitor"
description: "Guide to essential Aerospike database metrics for system health, alerting, and namespace memory monitoring."
---

# Key metrics to monitor

> For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt)
> 
> All documentation pages available in markdown.

Aerospike recommends that you monitor your system with the metrics listed on this page. For a complete list of metrics, see the [Metric reference](https://aerospike.com/docs/database/reference/metrics).

## Operating system and server health

-   Monitor system metrics with the [Prometheus Node Exporter](https://github.com/prometheus/node_exporter) or an OS-specific tool.
-   Use the The [Aerospike health monitor](https://aerospike.com/docs/database/observe/health-check) to detect health outliers.

## Finding total namespace memory

The metric `memory_used_bytes` was removed in Database 7.0.0 to streamline configuration and capacity planning, and to stabilize overhead so that memory usage calculations are more accurate. In Database 7.0.0, no single metric reports the amount of memory used in the namespace. A combination of items provide the same information as `memory_used_bytes`.

You allocated a specific amount of storage for your namespace when you created it. You also set a limit in the `system-memory-pct` parameter that tells Aerospike when the memory is full enough to stop writing to the namespace. Before you reach that limit, you can determine the total memory used in the namespace by adding the following individual metrics. Depending on which of the following is stored in memory in your namespace, add up the values to get the total used memory bytes:

-   `data_used_bytes`
-   `index_used_bytes`
-   `set_index_used_bytes`
-   `sindex_used_bytes`

You may also run the `info namespace` command in the Aerospike Admin (`asadm`) tool. See [Aerospike Admin - Info namespace](https://aerospike.com/docs/database/tools/asadm/live-mode/#namespace) for more information.

```plaintext
Admin> info namespace

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Namespace Usage Information (2023-10-13 15:59:46 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Namespace|           Node|Evictions|  Stop|~System Memory~|~Primary Index~~|~~Secondary~~~|~~~~~~~~~~~~~~~~~~~Storage Engine~~~~~~~~~~~~~~~~~~

         |               |         |Writes| Avail%| Evict%| Type|      Used|~~~~Index~~~~~|  Type|      Used| Used%|Evict%|  Used|Avail%|Avail

         |               |         |      |       |       |     |          | Type|    Used|      |          |      |      | Stop%|      |Stop%

bar      |172.17.0.3:3000|  0.000  |False |     74|      0|shmem|625.000 KB|shmem|0.000 B |memory|625.000 KB|0.06 %| 0.0 %|70.0 %|97.0 %|5.0 %

bar      |               |  0.000  |      |       |       |     |625.000 KB|     |0.000 B |      |625.000 KB|0.06 %|      |      |      |

test     |172.17.0.3:3000|  0.000  |False |     74|      0|shmem|625.000 KB|shmem|0.000 B |memory|625.000 KB|0.06 %| 0.0 %|70.0 %|87.0 %|5.0 %

test     |               |  0.000  |      |       |       |     |625.000 KB|     |0.000 B |      |625.000 KB|0.06 %|      |      |      |

Number of rows: 2
```

::: note
The metric `memory_used_bytes` was removed in Database 7.0.0 to streamline configuration and capacity planning, and to stabilize overhead so that memory usage calculations are more accurate.

In Database 7.0.0, no single metric reports the amount of memory used in the namespace. A combination of items provide the same information as `memory_used_bytes`.
:::

## Recommended alert metrics

-   [clock\_skew\_stop\_writes](https://aerospike.com/docs/database/reference/metrics#namespace__clock_skew_stop_writes)
-   [data\_avail\_pct](https://aerospike.com/docs/database/reference/metrics#namespace__data_avail_pct)
-   [dead\_partitions](https://aerospike.com/docs/database/reference/metrics#namespace__dead_partitions)
-   [device\_available\_pct](https://aerospike.com/docs/database/reference/metrics#namespace__device_available_pct)
-   [hwm\_breached](https://aerospike.com/docs/database/reference/metrics#namespace__hwm_breached)
-   [memory\_free\_pct](https://aerospike.com/docs/database/reference/metrics#namespace__memory_free_pct)
-   [pmem\_available\_pct](https://aerospike.com/docs/database/reference/metrics#namespace__pmem_available_pct)
-   [stop\_writes](https://aerospike.com/docs/database/reference/metrics#namespace__stop_writes)
-   [unavailable\_partitions](https://aerospike.com/docs/database/reference/metrics#namespace__unavailable_partitions)
-   [client\_connections](https://aerospike.com/docs/database/reference/metrics#node_stats__client_connections)
-   [client\_connections\_opened](https://aerospike.com/docs/database/reference/metrics#node_stats__client_connections_opened)
-   [cluster\_size](https://aerospike.com/docs/database/reference/metrics#node_stats__cluster_size)
-   [fabric\_connections\_opened](https://aerospike.com/docs/database/reference/metrics#node_stats__fabric_connections_opened)
-   [heartbeat\_connections\_opened](https://aerospike.com/docs/database/reference/metrics#node_stats__heartbeat_connections_opened)
-   [system\_free\_mem\_kbytes](https://aerospike.com/docs/database/reference/metrics#node_stats__system_free_mem_kbytes)
-   [system\_free\_mem\_pct](https://aerospike.com/docs/database/reference/metrics#node_stats__system_free_mem_pct)
-   [host\_free\_mem\_kbytes](https://aerospike.com/docs/database/reference/metrics#node_stats__host_free_mem_kbytes) — always reports host-level memory; compare with `system_free_mem_kbytes` when [`cgroup-mem-tracking`](https://aerospike.com/docs/database/reference/config#service__cgroup-mem-tracking) is enabled
-   [host\_free\_mem\_pct](https://aerospike.com/docs/database/reference/metrics#node_stats__host_free_mem_pct) — always reports host-level memory; compare with `system_free_mem_pct` when [`cgroup-mem-tracking`](https://aerospike.com/docs/database/reference/config#service__cgroup-mem-tracking) is enabled
-   [lag](https://aerospike.com/docs/database/reference/metrics#xdr__lag)

## Health-specific metrics

-   [`enable-health-check`](https://aerospike.com/docs/database/reference/config#service__enable-health-check)
-   [`health-stats`](https://aerospike.com/docs/database/reference/info#health-stats)
-   [`health-outliers`](https://aerospike.com/docs/database/reference/info#health-outliers)

## Other metrics to watch

-   [client\_delete\_error](https://aerospike.com/docs/database/reference/metrics#namespace__client_delete_error)
-   [client\_read\_error](https://aerospike.com/docs/database/reference/metrics#namespace__client_read_error)
-   [client\_udf\_error](https://aerospike.com/docs/database/reference/metrics#namespace__client_udf_error)
-   [client\_write\_error](https://aerospike.com/docs/database/reference/metrics#namespace__client_write_error)
-   [index\_flash\_alloc\_pct](https://aerospike.com/docs/database/reference/metrics#namespace__index_flash_alloc_pct)
-   [pi\_query\_aggr\_error](https://aerospike.com/docs/database/reference/metrics#namespace__pi_query_aggr_error)
-   [pi\_query\_long\_basic\_error](https://aerospike.com/docs/database/reference/metrics#namespace__pi_query_long_basic_error)
-   [pi\_query\_ops\_bg\_error](https://aerospike.com/docs/database/reference/metrics#namespace__pi_query_ops_bg_error)
-   [pi\_query\_short\_basic\_error](https://aerospike.com/docs/database/reference/metrics#namespace__pi_query_short_basic_error)
-   [pi\_query\_udf\_bg\_error](https://aerospike.com/docs/database/reference/metrics#namespace__pi_query_udf_bg_error)
-   [pi\_query\_udf\_bg\_error](https://aerospike.com/docs/database/reference/metrics#namespace__pi_query_udf_bg_error)
-   [scan\_aggr\_error](https://aerospike.com/docs/database/reference/metrics#namespace__scan_aggr_error)
-   [scan\_basic\_error](https://aerospike.com/docs/database/reference/metrics#namespace__scan_basic_error)
-   [scan\_ops\_bg\_error](https://aerospike.com/docs/database/reference/metrics#namespace__scan_ops_bg_error)
-   [scan\_udf\_bg\_error](https://aerospike.com/docs/database/reference/metrics#namespace__scan_udf_bg_error)
-   [storage\_engine\_device\_defrag\_q](https://aerospike.com/docs/database/reference/metrics#namespace__storage-engine.device%5Bix%5D.defrag_q)
-   [storage\_engine\_file\_write\_q](https://aerospike.com/docs/database/reference/metrics#namespace__storage-engine.file%5Bix%5D.write_q)
-   [batch\_index\_error](https://aerospike.com/docs/database/reference/metrics#node_stats__batch_index_error)
-   [heap\_efficiency\_pct](https://aerospike.com/docs/database/reference/metrics#node_stats__heap_efficiency_pct)
-   [rw\_in\_progress](https://aerospike.com/docs/database/reference/metrics#node_stats__rw_in_progress)
-   [abandoned](https://aerospike.com/docs/database/reference/metrics#xdr__abandoned)
-   [lap\_us](https://aerospike.com/docs/database/reference/metrics#xdr__lap_us)
-   [latency\_ms](https://aerospike.com/docs/database/reference/metrics#xdr__latency_ms)
-   [recoveries](https://aerospike.com/docs/database/reference/metrics#xdr__recoveries)
-   [recoveries\_pending](https://aerospike.com/docs/database/reference/metrics#xdr__recoveries_pending)
-   [retry\_conn\_reset](https://aerospike.com/docs/database/reference/metrics#xdr__retry_conn_reset)
-   [retry\_dest](https://aerospike.com/docs/database/reference/metrics#xdr__retry_dest)
-   [retry\_no\_node](https://aerospike.com/docs/database/reference/metrics#xdr__retry_no_node)
-   [success](https://aerospike.com/docs/database/reference/metrics#xdr__success)
-   [memory\_used\_bytes](https://aerospike.com/docs/database/reference/metrics#namespace__memory_used_bytes) (Removed in Database 7.0.0)