Collectinfo analyzer mode commands

This page describes Aerospike’s collectinfo-analyzer mode commands.

Overview

The collectinfo-analyzer displays data stored in a collectinfo archive instead of a running cluster. For information about commands that run in live cluster mode, see Live cluster mode commands.

To start the interactive shell in collectinfo-analyzer mode, run asadm -c -f COLLECTINFOPATH.
The -f parameter accepts the path of a single collectinfo file or a collectinfo directory path.

Note

The outputs shown on this page and in other asadm commands use abbreviations for certain numbers following the international system of kilo-, mega-, giga-, and so on referring to 1,000, 1,000,000, and 1,000,000,000. If no units are given such as B for “bytes”, the abbreviations should be read as counting discrete units.

Therefore, 2.660 K refers to 2,660 units.

Bundle diagnostics

Starting with Tools 13.1.0 (asadm 5.1.0), the collectinfo-analyzer checks each bundle when it opens it and prints a Collectinfo Bundle Diagnostics banner before any command output. The banner reports what is wrong with the bundle, and what was wrong with the cluster when the bundle was collected. It is automatic, and no flag enables or disables it.

• Interactive mode (asadm -c -f BUNDLE): the banner is part of the intro, after the list of snapshots. Each snapshot in the intro also has a Collected by: line naming the asadm version that collected the bundle, so the banner omits a collector-version finding that only repeats it.
• Execute mode (asadm -c -f BUNDLE -e "COMMAND"): the banner goes to stderr, so scripts that read stdout, including --json output, are unaffected. Under --json, the per-node error table is printed as plain lines.

Each finding has a severity of ERROR, WARNING, or INFO, and the most severe findings are listed first. INFO findings such as the collector version and the bundle’s age are normal on any older bundle and do not indicate a fault. The age finding appears when the bundle is at least seven days old.

In a bundle with more than one snapshot, the findings describe only the newest snapshot, and a finding says so.

Findings about the collection

These findings report whether the bundle was collected completely.

Bundles collected with Tools 13.1.0 or later carry collectinfo_meta.json, so findings about missing nodes are read from the collection record and are exact. For an older bundle, asadm infers missing nodes by comparing the nodes’ reported cluster_size with the nodes present, and the finding states that it names candidates rather than facts. asadm recovers the collector version from ascollectinfo.log for bundles that have no metadata, so the version finding works on older bundles too.

Finding	Meaning
Collected by asadm X	The asadm version that collected the bundle, and whether it is older or newer than the asadm analyzing it. Always stated.
Bundle metadata is format vN; this asadm understands vM	A newer collector wrote metadata that this asadm reads on a best-effort basis.
Bundle metadata could not be matched to the analyzed snapshot	The metadata is present but does not describe the snapshot.
Collection did not finish	The collection stopped partway.
Cluster nodes are missing from this bundle	From the metadata: how many nodes were collected, and each absent node with the reason.
This bundle may be missing cluster nodes	For an older bundle: inferred from cluster_size and labeled as an inference.
Node reconciliation did not complete during collection	The collection could not finish checking for missing nodes.
Collection was limited to the seed node or to N nodes	A deliberately partial collection, reported so it is not mistaken for a fault.
Nodes could not see each other at collection time	A heartbeat or network split, observed while collecting.
No system information in this bundle	No host-level data for any node, with the two possible causes.
System information covers N of M nodes	Partial host-level coverage.
SSH coverage gap	The nodes that the metadata records as having no host-level data.
Bundle has no sysinfo.log or aerospike.conf	Both files are collected only when asadm runs on a cluster node.
Collection failed for some sections on N nodes	A per-node table of the failed sections and the reason for each.
N transient collection errors recovered on retry	Nothing is missing as a result.
Some nodes answered only part of the collection	Nodes that are present but incomplete.
Bundle holds N snapshots; diagnostics describe only the newest	The banner covers the newest snapshot.
Bundle was collected N days ago	The bundle describes the cluster at collection time, not now.
Bundle contains no nodes or no Aerospike data for any node	ERROR. No command can report anything from this bundle. See Exit status.
N diagnostics could not be run against this bundle	A check that failed is named, rather than the banner claiming a completeness it cannot.

Findings about the cluster

These findings report problems in the cluster at the moment the bundle was collected. Earlier releases showed them only if you ran the right command or the deprecated health command. Where a finding suggests a next step, it names a current command such as show stop-writes, show best-practices, info namespace, show roster, or summary, rather than health.

Finding	Severity
The cluster was in stop-writes, naming the namespaces.	ERROR
Partitions were dead or unavailable, distinguishing lost data from unreadable data.	ERROR
Cluster membership was unhealthy, from a split or an integrity fault.	WARNING
The cluster was running more than one server version.	WARNING
Nodes were violating Aerospike best practices, naming the practices.	WARNING
The server flagged nodes as health outliers.	WARNING
Clock skew between nodes, measured against each namespace’s stop-writes threshold.	WARNING
Migrations were in progress, so object counts and storage figures are mid-flight.	INFO

Examples

A bundle collected by an older asadm from a host that is not a cluster node:

Collectinfo Bundle Diagnostics (2 warnings, 2 info)
 WARNING: No system information in this bundle
   No host-level data was captured for any of the 1 nodes, so nothing in the bundle describes their OS,
   CPU, memory, disks or network settings and `summary` reports no OS version.
   collectinfo gathers system statistics locally for the node it runs on and over SSH for every other
   node, so this bundle was either collected from a host that is not an Aerospike node without
   --enable-ssh, or collected with --enable-ssh and SSH failed for every node. This bundle records no
   collection flags, so the two cannot be told apart.
   The bundle also has no sysinfo.log and no aerospike.conf, which are only ever collected when asadm
   runs on a cluster node.
 WARNING: 1 node is violating Aerospike best-practices
   Violated: min-free-kbytes, swappiness, thp-enabled.
 INFO: Collected by asadm 3.2.2
 INFO: Bundle was collected 526 days ago
   Everything below describes the cluster as of 2025-04-01 17:20:10 UTC, not as it is now.

A bundle with collectinfo_meta.json that is missing nodes. Without the metadata, this bundle would look complete:

Collectinfo Bundle Diagnostics (4 warnings, 1 info)
 WARNING: Cluster nodes are missing from this bundle
   Collected 2 of 4 nodes asadm was connected to.
   1 node was connected to but returned no data, so it is absent from every command below:
     10.0.0.12:3000 (timed out)
   1 node was advertised as a cluster peer but never collected, so asadm never connected to it:
     10.0.0.15:3000 (advertised by 10.0.0.11:3000)
 WARNING: Nodes could not see each other at collection time
   Named in other nodes' peer lists but unreachable by them: 10.0.0.14:3000.
   Could not see every other node in the cluster: 10.0.0.14:3000.
   Recorded live while collecting, so it reflects the cluster at that moment.
   Check heartbeat configuration and the network between them.
 WARNING: Collection failed for some sections on 1 node
   Sections named alone are empty for those nodes: commands reading them show no rows rather than
   reporting an error.
   1 further error recovered on retry; nothing is missing as a result.
=============== Per-node collection errors ===============
          Node|           Sections|               Error
10.0.0.13:3000|statistics, sysinfo|ssh_error, timed out
 INFO: Collected by asadm 4.1.1

A bundle with no usable data, in execute mode:

Collectinfo Bundle Diagnostics (1 error, 1 info)
 ERROR: Bundle contains no Aerospike data for any of its 1 nodes
   asadm connected to these nodes but every information call failed, so no command can report
   anything: 10.0.0.11:3000.
   Re-collect from a host that can reach the cluster, raising --timeout if the nodes are slow to
   respond.

ERROR: Bundle contains no Aerospike data for any of its 1 nodes. No command can report anything from
this bundle.
$ echo $?
2

A complete bundle collected with current Tools shows only the collector version, plus any findings about the cluster itself.

Re-collect when the bundle is incomplete

When the banner reports missing nodes, missing system information, or an older collector, collect a new bundle with current Tools rather than analyzing the incomplete one. Older bundles still get the collector version and inferred findings, but only bundles collected with Tools 13.1.0 or later support exact node reconciliation. See collectinfo.

Exit status

In execute mode, asadm exits with status 2 when the bundle has no readable node data, and prints an ERROR line after the banner. Earlier releases printed empty tables and exited with status 0.

Note

This is the only finding that changes the exit status. A bundle whose banner reports warnings, or cluster problems such as stop-writes, still exits with status 0 when the command succeeds. Do not treat a WARNING as a failure in automation.

In interactive mode, the banner is printed and the shell continues.

Archive extraction

asadm extracts .tgz bundles with Python’s tar data filter, which rejects absolute paths, paths outside the destination directory, symlinks, and device files. Bundles collected by asadm contain only regular files and directories, so they are unaffected. An archive that asadm did not produce and that contains symlinks is rejected with a warning, instead of a later message that no valid collectinfo log is available:

WARNING: Could not extract FILE: REASON

features

The features command displays features used in cluster. It supports the like modifier.

Example: features command output

Collectinfo-analyzer> features
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Features (2020-12-18 02:09:28 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Node           |  10-0-0-1.heln.qwest.net:3000|  10-0-0-2.heln.qwest.net:3000|  10-0-0-3.heln.qwest.net:3000
AGGREGATION    |NO                            |NO                            |NO
BATCH          |NO                            |NO                            |NO
INDEX-ON-DEVICE|NO                            |NO                            |NO
INDEX-ON-PMEM  |NO                            |NO                            |NO
KVS            |YES                           |YES                           |YES
LDT            |NO                            |NO                            |NO
QUERY          |NO                            |NO                            |NO
RACK-AWARE     |NO                            |NO                            |NO
SC             |NO                            |NO                            |NO
SCAN           |NO                            |NO                            |NO
SECURITY       |NO                            |NO                            |NO
SINDEX         |NO                            |NO                            |NO
TLS (FABRIC)   |NO                            |NO                            |NO
TLS (HEARTBEAT)|NO                            |NO                            |NO
TLS (SERVICE)  |NO                            |NO                            |NO
UDF            |NO                            |NO                            |NO
XDR DESTINATION|NO                            |NO                            |NO
XDR SOURCE     |NO                            |NO                            |NO
Number of rows: 19

help

The help command provides a brief description of all supported commands.

info

Commands within info provide diagnostic information in a concise tabular format. Without additional arguments info executes network, namespace, and xdr sub-commands. Command output alerts you of potential cluster issues by coloring suspicious text red.

If cluster principal and node IDs are provided in the collectinfo archive, one Node value may appear in green with a * prefix — the node expected to be the Paxos Principal among nodes in the snapshot. Collectinfo mode has no self node, so cyan/@ self-node highlighting does not apply (unlike live cluster mode in Tools 13.0.2 and later).

For namespace and set subcommands, extra rows in blue show the sum of statistics per namespace and set.

dc

The info dc command displays a summary of important datacenter statistics for each datacenter.

Note

The info dc command was replaced by info xdr in Aerospike Database 5.0.0 and later.

The following example displays DC information for only one snapshot.

Example: info dc command output

Collectinfo-analyzer> info dc
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~DC Information (2020-12-18 18:12:25 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                          Node|         DC|  DC Type|Namespaces|     Lag|Records|    Avg|    Status
                              |           |         |          |        |Shipped|Latency|
                              |           |         |          |        |       |   (ms)|
  10-0-0-1.heln.qwest.net:3000|aerospike_b|aerospike|test      |00:00:00|  44452|     50|CLUSTER_UP
  10-0-0-2.heln.qwest.net:3000|aerospike_b|aerospike|test      |00:00:00|  45307|     52|CLUSTER_UP
  10-0-0-1.heln.qwest.net:3000|aerospike_c|aerospike|test      |00:00:00|  44452|     54|CLUSTER_UP
  10-0-0-2.heln.qwest.net:3000|aerospike_c|aerospike|test      |00:00:00|  45307|     56|CLUSTER_UP
Number of rows: 4

memory

The info memory command compares each node’s memory capacity with the memory the asd process had allocated when the bundle was collected. It requires Tools 13.1.0 (asadm 5.1.0) or later to analyze the bundle, and allocation figures require a bundle collected from Aerospike Database 8.2.0 or later.

info memory [-v | --verbose]

The tables, columns, and warnings are the same as for info memory in live cluster mode, and asadm prints them for each snapshot in the bundle. The with modifier is not available in collectinfo-analyzer mode, and the for modifier is rejected:

ERROR: info memory: the 'for' modifier is not supported. Host, cgroup, and heap values are per-node and cannot be filtered by namespace.

Bundles collected with Tools 13.1.0 or later also carry the output captured at collection time: summary.log holds the headline table and ascollectinfo.log holds the info memory -v output.

namespace

The info namespace command displays a summary of important namespace statistics for each namespace defined on each node ordered by Namespace and Node. It displays an extra row which is an aggregate of some of the statistics. When the primary or secondary index is stored on flash or pmem, extra usage statistics (including Used%) are displayed in the Primary Index and Secondary Index column groups. For shmem indexes, Used% appears in live-mode asadm 5.0.2 and later when indexes-memory-budget was configured on the captured cluster; collectinfo archives may not include that column depending on the asadm version that produced the capture.

With Tools 13.1.0 (asadm 5.1.0) or later, the Primary Index and Secondary Index column groups also have an Alloc column when the bundle was collected from Database 8.2.0 or later. It shows the bytes reserved by each index arena. For details, see info namespace in live cluster mode.

The info namespace command displays information in two tables:

• Namespace Usage Information: Namespace usage-related details.
• Namespace Object Information: Namespace object-related details.

Example: info namespace command output (collectinfo analyzer)

Collectinfo-analyzer> info namespace
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Namespace Usage Information (2026-07-20 11:33:05 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Namespace|                                      Node|Evictions|  Stop|~System Memory~|~~~~~~~~Primary Index~~~~~~~~|~~~~Secondary Index~~~~|~~~~~~~~~~~~~~~~~~Storage Engine~~~~~~~~~~~~~~~~~
         |                                          |         |Writes| Avail%|  Stop%| Type|      Used|Used%|Evict%| Type|      Used| Used%|  Type|    Used| Used%|Evict%|  Used|Avail%|Avail
         |                                          |         |      |       |       |     |          |     |      |     |          |      |      |        |      |      | Stop%|      |Stop%
test     |aerospike-a-0.test-runner.test-runner:4333|  0.000  |False |     74| 90.0 %|shmem| 52.688 KB|0.0 %| 0.0 %|shmem|160.000 MB|1.56 %|memory|3.122 MB|0.15 %|60.0 %|70.0 %|90.0 %|5.0 %
test     |*aerospike_a_1.test-runner:4333           |  0.000  |False |     74| 90.0 %|shmem| 52.125 KB|0.0 %| 0.0 %|shmem|160.000 MB|1.56 %|memory|3.063 MB|0.15 %|60.0 %|70.0 %|90.0 %|5.0 %
test     |aerospike_a_2.test-runner:4333            |  0.000  |False |     74| 90.0 %|shmem| 52.438 KB|0.0 %| 0.0 %|shmem|160.000 MB|1.56 %|memory|3.086 MB|0.15 %|60.0 %|70.0 %|90.0 %|5.0 %
test     |                                          |  0.000  |      |       |       |     |157.250 KB|0.0 %|      |     |480.000 MB|1.56 %|      |9.271 MB|0.15 %|      |      |      |
Number of rows: 3

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Namespace Object Information (2026-07-20 11:33:05 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Namespace|                                      Node|Rack|  Repl|Expirations|    Total|~~~~~~~~~~~~Objects~~~~~~~~~~~~|~~~~~~~~~Tombstones~~~~~~~~|~~~~Pending~~~~
         |                                          |  ID|Factor|           |  Records|   Master|    Prole|Non-Replica| Master|  Prole|Non-Replica|~~~~Migrates~~~
         |                                          |    |      |           |         |         |         |           |       |       |           |     Tx|     Rx
test     |aerospike-a-0.test-runner.test-runner:4333|   0|     2|    0.000  |843.000  |415.000  |428.000  |    0.000  |0.000  |0.000  |    0.000  |0.000  |0.000
test     |*aerospike_a_1.test-runner:4333           |   0|     2|    0.000  |834.000  |433.000  |401.000  |    0.000  |0.000  |0.000  |    0.000  |0.000  |0.000
test     |aerospike_a_2.test-runner:4333            |   0|     2|    0.000  |839.000  |410.000  |429.000  |    0.000  |0.000  |0.000  |    0.000  |0.000  |0.000
test     |                                          |    |      |    0.000  |  2.516 K|  1.258 K|  1.258 K|    0.000  |0.000  |0.000  |    0.000  |0.000  |0.000
Number of rows: 3

Optionally, use the info namespace usage or info namespace object commands to display namespace usage-related or object-related details only.

network

The info network command primarily serves as a translation table between Node, Node ID, and IP columns. It also provides cluster stats such as the cluster size, cluster key, number of client connections and uptime for each server.

Under the Node ID column, asadm also uses an asterisk to indicate the node which is expected to be the Paxos Principal.

Note

In live cluster mode, asadm marks a node with cyan and prefixes it with @ if the node is running on the same host as asadm itself. This appears only when you run asadm on a machine that is also a cluster node. A collectinfo archive has no notion of which node captured it, so this marking style never appears in collectinfo-analyzer mode.

Example: info network command output

Collectinfo-analyzer> info network
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Network Information (2020-12-16 21:45:32 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                          Node|         Node ID|             IP|    Build|Migrations|~~~~~~~~~~~~~~~~~~Cluster~~~~~~~~~~~~~~~~~~|Client|  Uptime
                              |                |               |         |          |Size|         Key|Integrity|      Principal| Conns|
  10-0-0-1.heln.qwest.net:3000| BB9010016AE4202|  10.0.0.1:3000|C-5.3.0.1|   0.000  |   5|92DCF600367B|True     |BB9050016AE4202|     2|00:07:48
  10-0-0-2.heln.qwest.net:3000| BB9020016AE4202|  10.0.0.2:3000|C-5.3.0.1|   0.000  |   5|92DCF600367B|True     |BB9050016AE4202|     2|00:07:47
  10-0-0-3.heln.qwest.net:3000| BB9030016AE4202|  10.0.0.3:3000|C-5.3.0.1|   0.000  |   5|92DCF600367B|True     |BB9050016AE4202|     2|00:07:46
  10-0-0-4.heln.qwest.net:3000| BB9040016AE4202|  10.0.0.4:3000|C-5.3.0.1|   0.000  |   5|92DCF600367B|True     |BB9050016AE4202|     3|00:07:46
  10-0-0-5.heln.qwest.net:3000|*BB9050016AE4202|  10.0.0.5:3000|C-5.3.0.1|   0.000  |   5|92DCF600367B|True     |BB9050016AE4202|     3|00:07:45
Number of rows: 5

release

The info release command displays a summary of release information for all cluster nodes, as shown in the following table.

Example: info release command output

Admin> info release
~~~~~~~~~~~~~~~~~~~~~~Release Information~~~~~~~~~~~~~~~~~~~~~~
            Node|Architecture|                     Edition|Version|   OS|                                     SHA|                                  EE SHA|                                FIPS SHA
192.168.1.1:3000|x86_64      |Aerospike Enterprise Edition|8.1.1.0|linux|3a3bc233f3f78b47fec2388fccdd66d55eb12cad|7a55a2e5b57e9af6fa773c4188ff9527687058e0|acc52654577aa3165d03f8d5556b083626e616e8
192.168.1.2:3000|x86_64      |Aerospike Enterprise Edition|8.1.1.0|linux|3a3bc233f3f78b47fec2388fccdd66d55eb12cad|7a55a2e5b57e9af6fa773c4188ff9527687058e0|acc52654577aa3165d03f8d5556b083626e616e8

The FIPS SHA column only appears if you’re using the Aerospike Server Enterprise for United States Federal Edition.

Note

The info release command requires Aerospike Database 8.1.1 and asadm 4.1.0, which is included in tools package 12.1.0.

The command fails if the installed version of either component does not meet the minimum requirement.

set

The info set command displays a summary of important set statistics for each set defined on each namespace on all nodes ordered by Set and Namespace. If configured, it displays details about your storage quotas. It includes an extra row which displays an aggregate of grouped rows.

Example: info set command output

Collectinfo-analyzer> info set
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Set Information (2023-03-21 23:18:54 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Namespace|    Set|           Node|    Memory|    Disk|~~~~~~Quota~~~~~~~|  Objects|  Stop| Disable|  Set
         |       |               |      Used|    Used|     Total|  Used%|         |Writes|Eviction|Index
         |       |               |          |        |          |       |         | Count|        |
test     |testset|172.17.0.3:3000| 37.534 KB|0.000 B | 48.828 KB|76.87 %|882.000  |     0|False   |No
test     |testset|172.17.0.4:3000| 37.326 KB|0.000 B | 48.828 KB|76.44 %|877.000  |     0|False   |No
test     |testset|172.17.0.5:3000| 38.353 KB|0.000 B | 48.828 KB|78.55 %|901.000  |     0|False   |No
test     |testset|               |113.213 KB|0.000 B |146.484 KB|77.29 %|  2.660 K|      |        |
test     |ufodata|172.17.0.3:3000| 32.640 KB|0.000 B |  0.000 B |     --|768.000  |     0|False   |No
test     |ufodata|172.17.0.4:3000| 30.479 KB|0.000 B |  0.000 B |     --|717.000  |     0|False   |No
test     |ufodata|172.17.0.5:3000| 35.700 KB|0.000 B |  0.000 B |     --|840.000  |     0|False   |No
test     |ufodata|               | 98.818 KB|0.000 B |  0.000 B |  0.0 %|  2.325 K|      |        |
Number of rows: 6

Run the show statistics command to display further statistics for specific sets.

 Collectinfo-analyzer> show statistics sets for test1 testset

sindex

The info sindex command displays a summary of important sindex statistics for each sindex defined on each namespace on all nodes ordered by Sindex and Node.

Example: info sindex command output

Collectinfo-analyzer> info sindex
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Secondary Index Information (2020-12-16 23:10:06 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Index Name|Namespace|    Set|         Node|    Bins|   Bin|State|Keys|~~~~~~~~~~Entries~~~~~~~~~~|~~~~Storage~~~~~|~~~~Queries~~~~~|~~~~Updates~~~~~|                              Context
           |         |       |             |        |  Type|     |    |  Total|  Avg Per|  Avg Per| Type|      Used|Requests|Avg Num|  Writes|Deletes|
           |         |       |             |        |      |     |    |         |    Rec|  Bin Val|     |          |    Recs|       |        |       |
name-sindex|bar      |testset|10.0.0.1:3000|    name|STRING|RW   |   2| 1.000 K | 1.000 | 0.500 K |shmem| 16.000 MB| 0.000  |0.000  | 5.000  |0.000  |--
name-sindex|bar      |testset|10.0.0.3:3000|    name|STRING|RW   |   2| 1.000 K | 1.000 | 0.500 K |shmem| 16.000 MB| 0.000  |0.000  | 5.000  |0.000  |--
name-sindex|bar      |testset|10.0.0.4:3000|    name|STRING|RW   |   2| 1.000 K | 1.000 | 0.500 K |shmem| 16.000 MB| 0.000  |0.000  | 3.000  |0.000  |--
name-sindex|bar      |testset|10.0.0.5:3000|    name|STRING|RW   |   2| 1.000 K | 1.000 | 0.500 K |shmem| 16.000 MB| 0.000  |0.000  | 4.000  |0.000  |--
name-sindex|bar      |testset|10.0.0.6:3000|    name|STRING|RW   |   2| 1.000 K | 1.000 | 0.500 K |shmem| 16.000 MB| 0.000  |0.000  | 3.000  |0.000  |--
           |bar      |testset|             |        |      |     |    | 5.000 K |       | 2.500 K |     | 80.000 MB| 0.000  |0.000  |20.000  |0.000  |--
age-sindex |test     |testset|10.0.0.3:3000|     age|STRING|RW   |   0|   0.000 | 1.000 |   0.000 |shmem| 16.000 MB| 0.000  |0.000  | 0.000  |0.000  |[list_index(-1), map_key(<string#11>)]
age-sindex |test     |testset|10.0.0.1:3000|     age|STRING|RW   |   0|   0.000 | 1.000 |   0.000 |shmem| 16.000 MB| 0.000  |0.000  | 0.000  |0.000  |[list_index(-1), map_key(<string#11>)]
age-sindex |test     |testset|10.0.0.4:3000|     age|STRING|RW   |   0|   0.000 | 1.000 |   0.000 |shmem| 16.000 MB| 0.000  |0.000  | 0.000  |0.000  |[list_index(-1), map_key(<string#11>)]
age-sindex |test     |testset|10.0.0.5:3000|     age|STRING|RW   |   0|   0.000 | 1.000 |   0.000 |shmem| 16.000 MB| 0.000  |0.000  | 0.000  |0.000  |[list_index(-1), map_key(<string#11>)]
age-sindex |test     |testset|10.0.0.6:3000|     age|STRING|RW   |   0|   0.000 | 1.000 |   0.000 |shmem| 16.000 MB| 0.000  |0.000  | 0.000  |0.000  |[list_index(-1), map_key(<string#11>)]
           |test     |testset|             |        |      |     |    |   0.000 | 1.000 |   0.000 |     | 80.000 MB| 0.000  |0.000  | 0.000  |0.000  |[list_index(-1), map_key(<string#11>)]
Number of rows: 10

Run the show statistics command to display further statistics for a specific secondary index.

 Collectinfo-analyzer> show statistics sindex for test test_str_idx

transactions

The info transactions command shows metrics for transaction monitors and provisionals. There are two sub-commands, info transactions monitors and info transactions provisionals, that filter the output to show only relevant metrics.

Only namespaces configured with strong consistency can show transaction information.

Monitors

A monitor is a small control record that represents one active transaction, stored in a hidden set <ERO~MRT> inside the namespace. While the client is running the transaction, the monitor tracks which digests (records) the client has written, the transaction timeout, and whether the client has started to commit. Completed transactions remove their monitors, leaving a tombstone.

Metric	Description
Count	Total number of monitor records observed for the namespace on the node.
Active	Number of monitors whose transactions are neither fully committed nor rolled back.
Tombstones	Durable-delete markers left after monitor records are removed.
Storage	Bytes used on device by the monitor set <ERO~MRT>.
Monitor Roll Back / Forward	Work performed by the monitor when it takes over an expired or abandoned transaction. Roll Forward completes a commit that had already started. Roll Back discards changes when no commit was started.

Provisionals

A provisional is the temporary version of an application record created when a transaction writes to that record. The original version remains unchanged and the provisional version holds the new data until the transaction commits or aborts.

Metric	Description
Provisionals	Count of provisional records, one per application record written inside a transaction.
Transaction (Blocked)	Number of writes rejected with AS_ERR_MRT_BLOCKED because a target record is locked by a transaction.
Transaction (Mismatch)	Number of commits rejected with AS_ERR_MRT_VERSION_MISMATCH when a record read earlier in the transaction changed before commit.
Verify Read	Results of the client’s commit-time generation checks on records read during the transaction.
Roll Back / Forward	Work applied to provisional records during cleanup or commit. Roll Forward commits updates from provisionals to live records, while Roll Back discards the update.

Example: info transactions command output

Collectinfo-analyzer> info transactions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~MRT Monitor Metrics (2025-07-17 05:32:16 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Namespace | Node                           | Count | Active | Tombstones | Storage  |~~~Monitor Roll Back~~~|~~~Monitor Roll Forward~~~
          |                                |       |        |            |          | Success | Error | Timeout | Success | Error | Timeout
db-1      | 1.0.0.127.in-addr.arpa:3000    | 0.000 | 0.000  | 59.000     | 3.988 MB | 2.478 K | 0.000 | 0.000   | 0.000   | 0.000 | 0.000
test      | 1.0.0.127.in-addr.arpa:3000    | 0.000 | 0.000  | 0.000      | --       | 0.000   | 0.000 | 0.000   | 0.000   | 0.000 | 0.000
Number of rows: 2

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~MRT Provisionals Metrics (2025-07-17 05:32:16 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Namespace | Node                           | Provisionals |~~~~Transaction~~~~| Version |~~~~~~Verify Read~~~~~~|~~~~~~~Roll Back~~~~~~~|~~~~~~Roll Forward~~~~~~
          |                                |              | Blocked | Mismatch |        | Success | Error | Timeout | Success | Error | Timeout | Success | Error | Timeout
db-1      | 1.0.0.127.in-addr.arpa:3000    | 0.000        | 0.000   | 0.000    | 0.000  | 0.000   | 0.000 | 0.000   | 2.478 K | 0.000 | 0.000   | 4.351 M | 0.000 | 0.000
test      | 1.0.0.127.in-addr.arpa:3000    | 0.000        | 0.000   | 0.000    | 0.000  | 0.000   | 0.000 | 0.000   | 0.000   | 0.000 | 0.000   | 0.000   | 0.000 | 0.000
Number of rows: 2

xdr

The info xdr command shows the current performance characteristics of XDR on each node.

Example: info xdr command output

Collectinfo-analyzer> info xdr
~~~~~~~~~~~~~~~~~~~~~~~~~~~~XDR Information DC1 (2020-12-17 00:11:48 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                          Node|Success|~~~~~~~~Retry~~~~~~~~~|Recoveries|       Lag|    Avg|Throughput
                              |       |Connection|Destination|   Pending|(hh:mm:ss)|Latency|   (rec/s)
                              |       |     Reset|           |          |          |   (ms)|
  10-0-0-3.heln.qwest.net:3000|    224|         0|          0|         0|  00:00:00|      0|      1078
  10-0-0-5.heln.qwest.net:3000|    223|         0|          0|         0|  00:00:00|      0|       970
                              |       |          |           |         0|          |      0|
Number of rows: 2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~XDR Information DC2 (2020-12-17 00:11:48 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                          Node|Success|~~~~~~~~Retry~~~~~~~~~|Recoveries|       Lag|    Avg|Throughput
                              |       |Connection|Destination|   Pending|(hh:mm:ss)|Latency|   (rec/s)
                              |       |     Reset|           |          |          |   (ms)|
  10-0-0-4.heln.qwest.net:3000|    199|         0|          0|         0|  00:00:00|      0|       898
  10-0-0-6.heln.qwest.net:3000|    201|         0|          0|         0|  00:00:00|      0|       988
                              |       |          |           |         0|          |      0|
Number of rows: 2

list

The list command displays the collectinfo currently added to collectinfo-analyzer.

Example: list command output

Collectinfo-analyzer> list
2017-03-08 07:04:33 UTC: /home/vagrant/shared/data/healthdata/remote_cluster

pager

The pager command enables scrollable output tables. This command gives an option to scroll each output table vertically or horizontally.

Use the following subcommands with pager:

• off: Disable paging and prints output normally.
• on: Enable output paging; similar to linux ‘less’.
• scroll: Display output in scrolling mode.

show

The show commands generally provide verbose output about the requested component. Most support the like modifier.

best-practices

Note

This command is supported in Database 5.7.0 and later.

The show best-practices command displays violations of Aerospike’s best-practices. See Best-Practices for detailed descriptions.

In the following example, node BB9010016AE4202 is violating two best practices, swappiness and thp-enabled. Node BB9030016AE4202 and BB9040016AE4202 are not violating any best practices and return ok.

Example: show best-practices

Collectinfo-analyzer> show best-practices
~Best Practices (2021-09-21 23:55:09 UTC)~
           Node|Response
BB9010016AE4202|swappiness, thp-enabled
BB9030016AE4202|ok
BB9040016AE4202|ok
Number of rows: 3

Following Aerospike's best-practices are required for optimal stability and performance.

config

The show config command displays Aerospike configuration settings. By default the command lists all server configuration parameters for security (added in Aerospike Tools 7.0.0, otherwise joined with service), service, network, namespace, and XDR. You can add one of the following sub-commands to limit the output to just those contexts:

• namespace
• network
• security
• service
• xdr

The following example requests all network configuration parameters containing the words heartbeat or mesh.

Example: show config command

Collectinfo-analyzer> show config network like heartbeat mesh
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Network Configuration (2020-12-17 01:07:36 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Node                        |  10-0-0-1.heln.qwest.net:3000|  10-0-0-2.heln.qwest.net:3000|  10-0-0-4.heln.qwest.net:3000|  10-0-0-5.heln.qwest.net:3000|  10-0-0-6.heln.qwest.net:3000
heartbeat.connect-timeout-ms|500                           |500                           |500                           |500                           |500
heartbeat.interval          |150                           |150                           |150                           |150                           |150
heartbeat.mode              |multicast                     |multicast                     |multicast                     |multicast                     |multicast
heartbeat.mtu               |1500                          |1500                          |1500                          |1500                          |1500
heartbeat.multicast-group   |239.1.99.200                  |239.1.99.200                  |239.1.99.200                  |239.1.99.200                  |239.1.99.200
heartbeat.port              |9918                          |9918                          |9918                          |9918                          |9918
heartbeat.protocol          |v3                            |v3                            |v3                            |v3                            |v3
heartbeat.timeout           |10                            |10                            |10                            |10                            |10
Number of rows: 9

We can use the diff modifier with show config commands to show differences between node configurations.

Example: show config command output

Collectinfo-analyzer> show config diff
~~~~~~~~~~~~~~~~~~~~~~~~~~Service Configuration (2020-12-17 01:09:07 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~
Node   |  10-0-0-1.heln.qwest.net:3000|  10-0-0-2.heln.qwest.net:3000|  10-0-0-4.heln.qwest.net:3000
pidfile|/var/run/aerospike/asd0.pid   |/var/run/aerospike/asd1.pid   |/var/run/aerospike/asd2.pid
Number of rows: 2

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Network Configuration (2020-12-17 01:09:07 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Node             |  10-0-0-1.heln.qwest.net:3000|  10-0-0-2.heln.qwest.net:3000|  10-0-0-4.heln.qwest.net:3000
heartbeat-address|192.168.120.110               |192.168.120.112               |192.168.120.113
Number of rows: 2

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~test Namespace Configuration (2020-12-17 01:09:07 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Node                         |  10-0-0-1.heln.qwest.net:3000|  10-0-0-2.heln.qwest.net:3000|  10-0-0-4.heln.qwest.net:3000
migrate-rx-partitions-initial|4036                          |3904                          |3614
migrate-tx-partitions-initial|3362                          |4096                          |4096
Number of rows: 3

~~~~~~~~~~~~~~~~~~~~bar Namespace Configuration (2020-12-17 01:09:07 UTC)~~~~~~~~~~~~~~~~~~~~~~~~
Node|  10-0-0-1.heln.qwest.net:3000|  10-0-0-2.heln.qwest.net:3000|  10-0-0-4.heln.qwest.net:3000
Number of rows: 1

For large clusters, use the -flip option to flip output table for simplicity and ease of understanding.

Example: show config command with -flip option

Collectinfo-analyzer> show config namespace like partition -flip
~~~~~~~~~~test Namespace Configuration (2020-12-17 01:19:14 UTC)~~~~~~~~~~
                          Node|partition-tree-sprigs|sindex.num-partitions
  10-0-0-1.heln.qwest.net:3000|                  256|                   32
  10-0-0-2.heln.qwest.net:3000|                  256|                   32
  10-0-0-4.heln.qwest.net:3000|                  256|                   32
  10-0-0-5.heln.qwest.net:3000|                  256|                   32
  10-0-0-6.heln.qwest.net:3000|                  256|                   32
Number of rows: 5

~~~~~~~~~~bar Namespace Configuration (2020-12-17 01:19:14 UTC)~~~~~~~~~~~
                          Node|partition-tree-sprigs|sindex.num-partitions
  10-0-0-1.heln.qwest.net:3000|                  256|                   32
  10-0-0-2.heln.qwest.net:3000|                  256|                   32
  10-0-0-4.heln.qwest.net:3000|                  256|                   32
  10-0-0-5.heln.qwest.net:3000|                  256|                   32
  10-0-0-6.heln.qwest.net:3000|                  256|                   32
Number of rows: 5

config xdr

The show config xdr command displays all the available configuration information related to XDR. By default, this command displays XDR configuration, XDR datacenter configuration, and XDR namespace configuration. You may also provide one of the sub-commands: dc, namespace, and filter to limit the output to a specific context. For example, to see configuration parameters for only namespace, use show config xdr namespace. All of the commands support the for, like, and diff modifiers.

The show config xdr dc command displays a new table for each configured datacenter. The command also supports the for modifier to filter by datacenter.

The following example gets XDR datacenter configuration parameters that contain max for datacenter dc2.

Example: show config xdr command with filter for datacenter

Collectinfo-analyzer> show config xdr dc for dc2 like max
~~~~~~~~~XDR dc2 DC Configuration (2023-02-16 22:37:00 UTC)~~~~~~~~~
Node                      |10.0.0.4:3000|10.0.0.5:3000|10.0.0.6:3000
max-recoveries-interleaved|0            |0            |0
max-used-service-threads  |0            |0            |0
Number of rows: 3

The show config xdr namespace command displays a new table for each configured XDR namespace. The command also supports the for modifier to filter first by namespace and then by datacenter.

The following example gets XDR namespace configuration parameters that contain sets for datacenter dc2.

Example: show config xdr command with filter for namespace

Collectinfo-analyzer> show config xdr namespace for test dc2 like sets
~~~~XDR test Namespace Configuration (2023-02-16 22:41:12 UTC)~~~~
Datacenter              |dc2          |dc2          |dc2
Node                    |10.0.0.4:3000|10.0.0.5:3000|10.0.0.6:3000
ignored-sets            |testset      |testset      |testset
ship-only-specified-sets|false        |false        |false
shipped-sets            |             |             |
Number of rows: 5

The show config xdr filter command displays the XDR filters that are set for a given namespace and datacenter. The command also supports the for modifier to filter first by datacenter and then by namespace.

Example: show config xdr with filters for datacenter and namespace

Collectinfo-analyzer> show config xdr filter
~~~~~~~~~~~~~~~~~~~~~~~XDR Filters (2023-02-16 22:55:02 UTC)~~~~~~~~~~~~~~~~~~~~~~~
Namespace|Datacenter|  Base64 Expression|                                Expression
bar      |dc2       |null               |null
test     |dc2       |kxGRSJMEk1ECo2FnZRU|or(is_tombstone(), ge(bin_int("age"), 21))
Number of rows: 2

distribution

The show distribution displays histograms and supports the object_size and time_to_live histograms. Output is only be displayed if you provide histogram information in collectinfo.

For object_size, set parameter -b to get bytewise distribution.

Example: show distribution command output

Collectinfo-analyzer> show distribution time_to_live
~~~~~~~~~~~~~~~~~~~~test - TTL Distribution in Seconds (2020-12-18 02:14:24 UTC)~~~~~~~~~~~~~~~~~~~~
          Percentage of records having ttl less than or equal to value measured in Seconds
                          Node|   10%|   20%|   30%|   40%|   50%|   60%|   70%|   80%|   90%|  100%
  10-0-0-1.heln.qwest.net:3000|427100|427100|427100|427100|427100|427100|427100|427100|427100|427100
  10-0-0-2.heln.qwest.net:3000|427100|427100|427100|427100|427100|427100|427100|427100|427100|427100
  10-0-0-3.heln.qwest.net:3000|427100|427100|427100|427100|427100|427100|427100|427100|427100|427100
  10-0-0-4.heln.qwest.net:3000|427100|427100|427100|427100|427100|427100|427100|427100|427100|427100
  10-0-0-6.heln.qwest.net:3000|427100|427100|427100|427100|427100|427100|427100|427100|427100|427100
Number of rows: 5

~~~~~~~~~~~~~~~~~~~~bar - TTL Distribution in Seconds (2020-12-18 02:14:24 UTC)~~~~~~~~~~~~~~~~~~~~~
          Percentage of records having ttl less than or equal to value measured in Seconds
                          Node|   10%|   20%|   30%|   40%|   50%|   60%|   70%|   80%|   90%|  100%
  10-0-0-1.heln.qwest.net:3000|425500|425500|425500|425500|425500|425500|425500|425500|425500|425500
  10-0-0-2.heln.qwest.net:3000|425500|425500|425500|425500|425500|425500|425500|425500|425500|425500
  10-0-0-3.heln.qwest.net:3000|425500|425500|425500|425500|425500|425500|425500|425500|425500|425500
  10-0-0-4.heln.qwest.net:3000|425500|425500|425500|425500|425500|425500|425500|425500|425500|425500
  10-0-0-6.heln.qwest.net:3000|425500|425500|425500|425500|425500|425500|425500|425500|425500|425500
Number of rows: 5

jobs

The show jobs [scan|query|sindex-builder] command in conjunction with the manage jobs controller displays current and past jobs running on the Aerospike cluster. To make viewing easier, run the pager on command first.

By default all job modules are shown, grouped by their Namespace and Type. Groups are separated by dashes. Jobs are further organized left to right by their Progress % and Time Since Done.

Starting in Tools 13.0.2, show jobs queries supports -flip, like, for, trid, and -where modifiers to filter and project output on large captures. See Filter and project job output in live cluster mode.

Example: collectinfo-analyzer flip, like, and -where

Collectinfo-analyzer> show jobs queries like "^(set|status|rps)$" -flip -where status=done
                                       Node|Namespace|          Type|Progress%|      Transaction ID|...|    rps| set|  status
aerospike_a_1.test-runner:4333             |test     |background-udf|  100.0 %|11605936893403822497|...|1.000  |demo|done(ok)
Number of rows: 3

Note

sindex-builder jobs were removed in Database 5.7.0.

Collectinfo-analyzer> show jobs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Scan Jobs (2021-10-20 23:08:14 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Node              |10.0.0.3:3000       |10.0.0.2:3000                   |10.0.0.1:3000
Namespace         |bar                 |bar                             |bar
Module            |scan                |scan                            |scan
Type              |basic               |basic                           |basic
Progress %        |100.0               |100.0                           |100.0
Transaction ID    |1583278212325152813 |1554763604191518487             |1554763604191518487
Time Since Done   |00:33:26            |00:34:42                        |00:34:43
active-threads    |0                   |0                               |0
from              |10.0.22.1+52252     |10.0.22.1+34048                 |10.0.22.1+40340
n-pids-requested  |1.366 K             |1.365 K                         |1.365 K
net-io-bytes      |37.940 MB           |8.505 MB                        |8.048 MB
priority          |0                   |0                               |0
recs-failed       |0.000               |0.000                           |0.000
recs-filtered-bins|0.000               |0.000                           |0.000
recs-filtered-meta|0.000               |0.000                           |0.000
recs-succeeded    |333.874 K           |75.826 K                        |71.779 K
recs-throttled    |333.874 K           |75.826 K                        |71.779 K
rps               |0.000               |0.000                           |0.000
run-time          |00:00:05            |00:00:01                        |00:00:01
socket-timeout    |00:00:30            |00:00:30                        |00:00:30
status            |done(ok)            |done(abandoned-response-timeout)|done(abandoned-response-timeout)
-------------------------------------------------------------------------------------------------------------------
Node              |10.0.0.3:3000       |10.0.0.2:3000                   |10.0.0.1:3000
Namespace         |test                |test                            |test
Module            |scan                |scan                            |scan
Type              |basic               |basic                           |basic
Progress %        |100.0               |100.0                           |100.0
Transaction ID    |17709699727074092152|17709699727074092152            |17709699727074092152
Time Since Done   |00:47:59            |00:47:59                        |00:47:59
active-threads    |0                   |0                               |0
from              |10.0.22.1+51868     |10.0.22.1+33716                 |10.22.22.1+40008
n-pids-requested  |1.366 K             |1.365 K                         |1.365 K
net-io-bytes      |438.377 KB          |443.145 KB                      |442.441 KB
priority          |0                   |0                               |0
recs-failed       |0.000               |0.000                           |0.000
recs-filtered-bins|0.000               |0.000                           |0.000
recs-filtered-meta|0.000               |0.000                           |0.000
recs-succeeded    |3.308 K             |3.349 K                         |3.343 K
recs-throttled    |3.308 K             |3.349 K                         |3.343 K
rps               |0.000               |0.000                           |0.000
run-time          |00:00:00            |00:00:00                        |00:00:00
socket-timeout    |00:00:30            |00:00:30                        |00:00:30
status            |done(ok)            |done(ok)                        |done(ok)
Number of rows: 42

~~~~~~~~~~~~~~~~~~~~~Query Jobs (2021-10-20 23:08:14 UTC)~~~~~~~~~~~~~~~~~~~~~
Node              |10.0.0.1:3000      |10.0.0.3:3000      |10.0.0.2:3000
Namespace         |bar                |bar                |bar
Module            |query              |query              |query
Progress %        |0.0                |0.0                |0.0
Transaction ID    |2143237531128163351|2143237531128163351|2143237531128163351
Time Since Done   |00:00:00           |00:00:00           |00:00:00
active-threads    |0                  |0                  |0
net-io-bytes      |2.400 MB           |2.087 MB           |2.681 MB
priority          |10                 |10                 |10
recs-failed       |0.000              |0.000              |0.000
recs-filtered-bins|0.000              |0.000              |0.000
recs-filtered-meta|0.000              |0.000              |0.000
recs-succeeded    |32.558 K           |29.274 K           |36.467 K
recs-throttled    |0.000              |0.000              |0.000
rps               |0.000              |0.000              |0.000
run-time          |00:00:07           |00:00:07           |00:00:07
set               |testset            |testset            |testset
sindex-name       |a-bar-index        |a-bar-index        |a-bar-index
socket-timeout    |00:00:00           |00:00:00           |00:00:00
status            |active             |active             |active
Number of rows: 20

latencies

The show latencies command displays latencies characteristics of reads, writes, queries, replication, and UDF. Output is only displayed if you provide latency information in collectinfo.

Example: latencies for write_master

Collectinfo-analyzer> show latencies -v like write-master
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Latency  (2020-12-17 19:19:12 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Namespace|   Histogram|           Node|ops/sec|>1ms|>2ms|>4ms|>8ms|>16ms|>32ms|>64ms|>128ms|>256ms|>512ms|>1024ms|>2048ms|>4096ms|>8192ms|>16384ms|>32768ms|>65536ms
test     |write-master|  10.0.0.1:3000|0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
test     |write-master|  10.0.0.2:3000|0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
test     |write-master|  10.0.0.4:3000|0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
test     |write-master|  10.0.0.5:3000|0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
test     |write-master|  10.0.0.6:3000|0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
         |            |               |0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
Number of rows: 5

latency

Removed in asadm 0.7.0.

The show latency command displays latency characteristics of reads, writes, and proxies. Output is only displayed if you provide latency information in collectinfo.

Example: latency for writes_master

Collectinfo-analyzer> show latency -v like writes_master
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Latency  (2020-12-17 02:08:39 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Namespace|   Histogram|                          Node|ops/sec|>1ms|>2ms|>4ms|>8ms|>16ms|>32ms|>64ms|>128ms|>256ms|>512ms|>1024ms|>2048ms|>4096ms|>8192ms|>16384ms|>32768ms|>65536ms
test     |write-master|  10-0-0-1.heln.qwest.net:3000|0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
test     |write-master|  10-0-0-2.heln.qwest.net:3000|0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
test     |write-master|  10-0-0-4.heln.qwest.net:3000|0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
test     |write-master|  10-0-0-5.heln.qwest.net:3000|0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
test     |write-master|  10-0-0-6.heln.qwest.net:3000|0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
         |            |                              |0.0    |0.0 |0.0 |0.0 |0.0 |0.0  |0.0  |0.0  |0.0   |0.0   |0.0   |0.0    |0.0    |0.0    |0.0    |0.0     |0.0     |0.0
Number of rows: 5

pmap

The show pmap command displays partition map analysis of the Aerospike cluster. Output is only displayed if you provide partition information in collectinfo.

Example: show map command output

Collectinfo-analyzer> show pmap
~~~~~~~~~~~~~~~~~~~~Partition Map Analysis (2020-12-18 01:12:36 UTC)~~~~~~~~~~~~~~~~~~~~
Namespace|                          Node| Cluster Key|~~~~~~~~~~~~Partitions~~~~~~~~~~~~
         |                              |            |Primary|Secondary|Unavailable|Dead
bar      |  10-0-0-1.heln.qwest.net:3000|33718FC58CD6|    791|      799|          0|   0
bar      |  10-0-0-2.heln.qwest.net:3000|33718FC58CD6|    868|      822|          0|   0
bar      |  10-0-0-3.heln.qwest.net:3000|33718FC58CD6|    839|      862|          0|   0
bar      |  10-0-0-4.heln.qwest.net:3000|33718FC58CD6|    800|      780|          0|   0
bar      |  10-0-0-6.heln.qwest.net:3000|33718FC58CD6|    798|      833|          0|   0
bar      |                              |            |   4096|     4096|          0|   0
test     |  10-0-0-1.heln.qwest.net:3000|33718FC58CD6|    791|      799|          0|   0
test     |  10-0-0-2.heln.qwest.net:3000|33718FC58CD6|    868|      822|          0|   0
test     |  10-0-0-3.heln.qwest.net:3000|33718FC58CD6|    839|      862|          0|   0
test     |  10-0-0-4.heln.qwest.net:3000|33718FC58CD6|    800|      780|          0|   0
test     |  10-0-0-6.heln.qwest.net:3000|33718FC58CD6|    798|      833|          0|   0
test     |                              |            |   4096|     4096|          0|   0
Number of rows: 10

• Primary Partitions: Total number of primary partitions for a specific namespace on that node.
• Secondary Partitions: Total number of secondary partitions for a specific namespace on that node.
• Unavailable Partitions: The number of partitions that are unavailable when roster nodes are missing.
• Dead Partitions: The number of partitions that are unavailable when all roster nodes are present.

racks

The show racks command displays a namespace’s rack IDs and the nodes assigned to each. This is particularly useful in rack awareness configurations.

Collectinfo-analyzer> show racks
~~~~~~~~~~~~~~~~Racks (2021-10-21 20:33:28 UTC)~~~~~~~~~~~~~~~~~
Namespace|Rack|                                            Nodes
         |  ID|
bar      |4   |BB9040016AE4202, BB9020016AE4202, BB9010016AE4202
test     |2   |BB9040016AE4202, BB9010016AE4202
Number of rows: 2

roles

The show roles command displays roles along with associated privileges, allowlist, and quotas as returned by the principal node.

Example: show roles command output

Collectinfo-analyzer> show roles
~~~~~~~~~~~~~~~~~~~~~~~~~~~Roles (2021-04-21 22:28:01 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Role|                                       Privileges|Allowlist|~~~Quotas~~
              |                                                 |         | Read|Write
read          |                                             read|       --|--   |--
read-write    |                                       read-write|       --|--   |--
read-write-udf|                                   read-write-udf|       --|--   |--
reader        |                                             read|  1.1.1.1|10000|1
root          |    user-admin, sys-admin, data-admin, read-write|       --|--   |--
superuser     |user-admin, sys-admin, data-admin, read-write-udf|       --|--   |--
sys-admin     |                                        sys-admin|       --|--   |--
user-admin    |                                       user-admin|       --|--   |--
write         |                                            write|       --|--   |--
writer        |                                       read-write|  2.2.2.2|1    |10000
Number of rows: 10

roster

The show roster command displays the current and pending roster as well as the observed nodes. To make viewing easier, run the pager on command first. To filter output based on namespace, use the for modifier. To display any differences between values in any given column, use the diff modifier.

Example: show roster command output

Collectinfo-analyzer> show roster
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Roster (2021-10-21 20:12:29 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         Node|         Node ID|Namespace|                                         Current Roster|                                         Pending Roster|                                         Observed Nodes
10.0.0.1:3000|BB9010016AE4202 |bar      |BB9040016AE4202@4, BB9020016AE4202@4, BB9010016AE4202@4|BB9040016AE4202@4, BB9020016AE4202@4, BB9010016AE4202@4|BB9040016AE4202@4, BB9020016AE4202@4, BB9010016AE4202@4
10.0.0.2:3000|BB9020016AE4202 |bar      |BB9040016AE4202@4, BB9020016AE4202@4, BB9010016AE4202@4|BB9040016AE4202@4, BB9020016AE4202@4, BB9010016AE4202@4|BB9040016AE4202@4, BB9020016AE4202@4, BB9010016AE4202@4
10.0.0.4:3000|*BB9040016AE4202|bar      |BB9040016AE4202@4, BB9020016AE4202@4, BB9010016AE4202@4|BB9040016AE4202@4, BB9020016AE4202@4, BB9010016AE4202@4|BB9040016AE4202@4, BB9020016AE4202@4, BB9010016AE4202@4
10.0.0.1:3000|BB9010016AE4202 |test     |BB9040016AE4202@2, BB9020016AE4202@2, BB9010016AE4202@2|BB9040016AE4202@2, BB9020016AE4202@2, BB9010016AE4202@2|BB9040016AE4202@2, BB9020016AE4202@2, BB9010016AE4202@2
10.0.0.2:3000|BB9020016AE4202 |test     |BB9040016AE4202@2, BB9020016AE4202@2, BB9010016AE4202@2|BB9040016AE4202@2, BB9020016AE4202@2, BB9010016AE4202@2|BB9040016AE4202@2, BB9020016AE4202@2, BB9010016AE4202@2
10.0.0.4:3000|*BB9040016AE4202|test     |BB9040016AE4202@2, BB9020016AE4202@2, BB9010016AE4202@2|BB9040016AE4202@2, BB9020016AE4202@2, BB9010016AE4202@2|BB9040016AE4202@2, BB9020016AE4202@2, BB9010016AE4202@2
Number of rows: 6

sindex

The show sindex command displays secondary indexes and associated static metadata as returned by the principal node.

Example: show sindex command output

Collectinfo-analyzer> show sindex
~~~~~~Secondary Indexes (2021-01-22 23:04:49 UTC)~~~~~~
 Index Name|Namespace| Set| Bin|    Bin|    Index|State
           |         |    |    |   Type|     Type|
name-sindex|bar      |NULL|name|STRING |NONE     |RW
age-index  |test     |NULL| age|NUMERIC|MAPVALUES|RW
job-index  |test     |NULL| age|STRING |MAPVALUES|RW
Number of rows: 3

Secondary index on a nested context

A secondary index may be created on a Map (document) or List data type bin to identify a value of that type to index. The show sindex command displays the nested index with a Context that identifies the base64 encoded value. In this example, a bin report has a Map type and within it there’s a map key shape holding a list of strings.

Example: show roles for nested index command output

Collectinfo-analyzer> show sindex
~~~~~~~~~~~~~~~~Secondary Indexes (2023-01-11 00:58:31 UTC)~~~~~~~~~~~~~~~~
    Index|Namespace|    Set|   Bin|   Bin|Index|State|              Context
     Name|         |       |      |  Type| Type|     |
shape-idx|sandbox  |ufodata|report|string|list |RW   |[map_key(<string#5>)]
Number of rows: 1

Secondary index on an expression

A secondary index may also be created on an expression rather than a bin, using either a compiled expression (exp_base64) or Aerospike Expression Language (AEL) source (ael or ael_b64, Database 8.2.0 and later). Live mode and collectinfo-analyzer mode render show sindex through the same asadm view templates, so the Expression and AEL columns follow the rules described for show sindex in live mode.

In this example, mod100-idx and mod100-ael-idx both index the same computed value (id modulo 100), but were created two different ways. mod100-idx was created from a compiled expression, so the Expression column displays the server’s human-readable rendering and AEL displays --. mod100-ael-idx was created from AEL, so the AEL column displays the original AEL source text verbatim and Expression displays --.

Example: show sindex command output with expression indexes

Collectinfo-analyzer> show sindex
~~~~~~~~~~~~~~~~~~~~~~~~Secondary Indexes (2026-09-24 18:33:10 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~
    Index Name|Namespace|  Set| Bin|    Bin|  Index|State|             Expression|       AEL
              |         |     |    |   Type|   Type|     |                       |
mod100-ael-idx|test     |posts|null|integer|default|RW   |--                     |$.id % 100
mod100-idx    |test     |posts|null|integer|default|RW   |mod(bin_int("id"), 100)|--
Number of rows: 2

The AEL column requires a bundle collected with Tools 13.1.0 (asadm 5.1.0) or later. In a bundle collected with an earlier asadm, an AEL index has no AEL value, and the Expression column shows the server’s rendering of the compiled AEL instead.

See creating a secondary index with asadm.

statistics

The show statistics command displays all server statistics from several server components. By default it returns statistics for the following:

• bins
• namespace
• service
• sets
• sindex
• xdr

Use the bins, namespace, service, sets, sindex, and xdr sub-commands to limit the output to a single context.

See details and additional subcommands for show config xdr. You can also use the -t parameter to show an extra aggregate column for total across columns. Total column displays sum of statistics with numeric values.

The following example shows service-level statistics, filters for metrics containing the token batch, and displays a total column.

Example: show statistics commmand

Collectinfo-analyzer> show statistics service like batch -t
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Service Statistics (2020-12-18 01:33:36 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Node                                 |  10-0-0-1.heln.qwest.net:3000|  10-0-0-2.heln.qwest.net:3000|  10-0-0-3.heln.qwest.net:3000|
batch_index_complete                 |0                             |0                             |0                             |0
batch_index_created_buffers          |0                             |0                             |0                             |0
batch_index_delay                    |0                             |0                             |0                             |0
batch_index_destroyed_buffers        |0                             |0                             |0                             |0
batch_index_error                    |0                             |0                             |0                             |0
batch_index_huge_buffers             |0                             |0                             |0                             |0
batch_index_initiate                 |0                             |0                             |0                             |0
batch_index_proto_compression_ratio  |1.0                           |1.0                           |1.0                           |3.0
batch_index_proto_uncompressed_pct   |0.0                           |0.0                           |0.0                           |0.0
batch_index_queue                    |0:0,0:0                       |0:0,0:0                       |0:0,0:0                       |
batch_index_timeout                  |0                             |0                             |0                             |0
batch_index_unused_buffers           |0                             |0                             |0                             |0
early_tsvc_batch_sub_error           |0                             |0                             |0                             |0
early_tsvc_from_proxy_batch_sub_error|0                             |0                             |0                             |0
Number of rows: 15

For large clusters, use the -flip option to flip the output for readability.

Example: show statistics commmand output

Collectinfo-analyzer> show statistics namespace for test like migrate_tx_partitions_i -flip
~~~~~~~~~~~~~~~~~~~~test Namespace Statistics (2020-12-18 02:08:43 UTC)~~~~~~~~~~~~~~~~~~~~~
                          Node|migrate_tx_partitions_imbalance|migrate_tx_partitions_initial
  10-0-0-1.heln.qwest.net:3000|                              0|                          390
Number of rows: 1

statistics xdr

The show statistics xdr command displays all the available statistics information related to xdr. By default, this command displays xdr datacenter statistics and xdr namespace statistics. You may also provide one of the sub-commands dc and namespace to limit the output to a specific context.

The show statistics xdr dc command displays a new table for each configured datacenter. The command also supports the for modifier to filter by datacenter.

Example: show statistics xdr dc command for each datacenter

Collectinfo-analyzer> show statistics xdr dc for dc2 like retry
~~~~~~~~~XDR dc2 DC Statistics (2023-02-16 23:56:28 UTC)~~~~~~~~~~
Node            |172.17.0.4:3000|172.17.0.5:3000|172.17.0.6:3000
retry_conn_reset|0              |0              |0
retry_dest      |0              |0              |0
retry_no_node   |0              |0              |0
Number of rows: 4

The show statistics xdr namespace command displays a new table for each configured xdr namespace. The command also supports the for modifier to filter first by namespace and then by datacenter.

Example: show roles command for each namespace

Collectinfo-analyzer> show statistics xdr namespace like retry
~~~~~~~~~~~~~~~~~~~~~~XDR test Namespace Statistics (2023-02-16 23:57:32 UTC)~~~~~~~~~~~~~~~~~~~~~~~
Datacenter      |dc1          |dc1          |dc1          |dc2          |dc2          |dc2
Node            |10.0.0.4:3000|10.0.0.5:3000|10.0.0.6:3000|10.0.0.4:3000|10.0.0.5:3000|10.0.0.6:3000
retry_conn_reset|0            |0            |0            |0            |0            |0
retry_dest      |0            |0            |0            |0            |0            |0
retry_no_node   |0            |0            |0            |0            |0            |0
Number of rows: 5

~~~~~~~~~~~~~~~~~~~~~~XDR bar Namespace Statistics (2023-02-16 23:57:32 UTC)~~~~~~~~~~~~~~~~~~~~~~~
Datacenter      |dc1          |dc1          |dc1          |dc2          |dc2          |dc2
Node            |10.0.0.4:3000|10.0.0.5:3000|10.0.0.6:3000|10.0.0.4:3000|10.0.0.5:3000|10.0.0.6:3000
retry_conn_reset|0            |0            |0            |0            |0            |0
retry_dest      |0            |0            |0            |0            |0            |0
retry_no_node   |0            |0            |0            |0            |0            |0
Number of rows: 5

To instead display a new table for each configured datacenter use the --by-dc flag.

Example: show roles command with --by-dc flag

Collectinfo-analyzer> show statistics xdr namespace like retry --by-dc
~~~~~~~~~~~~~~~~~~~~~~XDR dc1 Namespace Statistics (2023-02-16 23:57:32 UTC)~~~~~~~~~~~~~~~~~~~~~~~
Namespace       |test         |test         |test         |bar          |bar          |bar
Node            |10.0.0.4:3000|10.0.0.5:3000|10.0.0.6:3000|10.0.0.4:3000|10.0.0.5:3000|10.0.0.6:3000
retry_conn_reset|0            |0            |0            |0            |0            |0
retry_dest      |0            |0            |0            |0            |0            |0
retry_no_node   |0            |0            |0            |0            |0            |0
Number of rows: 5

~~~~~~~~~~~~~~~~~~~~~~XDR dc2 Namespace Statistics (2023-02-16 23:57:32 UTC)~~~~~~~~~~~~~~~~~~~~~~~
Namespace       |test         |test         |test         |bar          |bar          |bar
Node            |10.0.0.4:3000|10.0.0.5:3000|10.0.0.6:3000|10.0.0.4:3000|10.0.0.5:3000|10.0.0.6:3000
retry_conn_reset|0            |0            |0            |0            |0            |0
retry_dest      |0            |0            |0            |0            |0            |0
retry_no_node   |0            |0            |0            |0            |0            |0
Number of rows: 5

stop-writes

The show stop-writes command returns comprehensive information about stop-writes configuration parameters, metrics, and their associated namespace and test contexts. show stop-writes helps determine the proximity to reaching the stop-writes threshold at different levels: service context (global), namespace context, or set context. It also helps identify the reasons for being in the stop-writes state.

show stop-writes displays the following table which is ordered based on the proximity to breaching the configured stop-writes threshold. For instance, the stop-writes-count configuration for the namespace test and set testset is closest to reaching the limit of 10,000 records and is positioned at the bottom of the table. This arrangement helps in effectively addressing the issue by providing the relevant configuration details and the metric that might potentially exceed the threshold. Additionally, the table presents the current proximity to the configured threshold, actual usage, and the threshold itself, offering a clear understanding of the current status. A -- threshold means none is configured.

Note

For shmem primary indexes, show stop-writes compares combined index memory usage against indexes-memory-budget, matching the server’s index stop-writes check. flash and pmem primary indexes are not RAM-budgeted and are excluded from this check. Their mount-usage proximity appears in info namespace usage.

health

As of Tools 13.0.2 / asadm 5.0.2, the health command (including health -v) is deprecated, is no longer actively maintained, and prints a warning to that effect. It will be removed in a future release. For the stop-writes and index-usage checks health -v used to perform, use show stop-writes as described above.

Example: show stop-writes command output

Collectinfo-analyzer> show stop-writes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Stop Writes (2023-05-23 23:01:01 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                          Show all stop writes - add 'for <namespace> [<set>]' for a shorter list.
                    Config|Namespace|    Set|           Node|Stop-Writes|               Metric| Usage%|     Usage|Threshold
stop-writes-size          |test     |testset|172.17.0.5:3000|False      |memory_data_bytes    |     --|123.005 KB|       --
stop-writes-size          |test     |testset|172.17.0.4:3000|False      |memory_data_bytes    |     --|123.373 KB|       --
stop-writes-size          |test     |testset|172.17.0.3:3000|False      |memory_data_bytes    |     --|123.246 KB|       --
--                        |test     |--     |172.17.0.5:3000|False      |cluster_clock_skew_ms|     --|  00:00:00|       --
--                        |bar      |--     |172.17.0.5:3000|False      |cluster_clock_skew_ms|     --|  00:00:00|       --
--                        |test     |--     |172.17.0.4:3000|False      |cluster_clock_skew_ms|     --|  00:00:00|       --
--                        |bar      |--     |172.17.0.4:3000|False      |cluster_clock_skew_ms|     --|  00:00:00|       --
--                        |test     |--     |172.17.0.3:3000|False      |cluster_clock_skew_ms|     --|  00:00:00|       --
--                        |bar      |--     |172.17.0.3:3000|False      |cluster_clock_skew_ms|     --|  00:00:00|       --
stop-writes-pct           |bar      |--     |172.17.0.3:3000|False      |memory_used_bytes    |  0.0 %|  0.000 B | 3.600 GB
stop-writes-pct           |bar      |--     |172.17.0.4:3000|False      |memory_used_bytes    |  0.0 %|  0.000 B | 3.600 GB
stop-writes-pct           |bar      |--     |172.17.0.5:3000|False      |memory_used_bytes    |  0.0 %|  0.000 B | 3.600 GB
stop-writes-pct           |test     |--     |172.17.0.5:3000|False      |memory_used_bytes    | 1.74 %|728.567 KB|40.960 MB
stop-writes-pct           |test     |--     |172.17.0.3:3000|False      |memory_used_bytes    | 1.74 %|729.996 KB|40.960 MB
stop-writes-pct           |test     |--     |172.17.0.4:3000|False      |memory_used_bytes    | 1.74 %|730.748 KB|40.960 MB
stop-writes-sys-memory-pct|bar      |--     |172.17.0.3:3000|False      |system_free_mem_pct  |28.89 %|    26.0 %|   90.0 %
stop-writes-sys-memory-pct|test     |--     |172.17.0.3:3000|False      |system_free_mem_pct  |28.89 %|    26.0 %|   90.0 %
stop-writes-sys-memory-pct|bar      |--     |172.17.0.4:3000|False      |system_free_mem_pct  |28.89 %|    26.0 %|   90.0 %
stop-writes-sys-memory-pct|test     |--     |172.17.0.4:3000|False      |system_free_mem_pct  |28.89 %|    26.0 %|   90.0 %
stop-writes-sys-memory-pct|bar      |--     |172.17.0.5:3000|False      |system_free_mem_pct  |28.89 %|    26.0 %|   90.0 %
stop-writes-sys-memory-pct|test     |--     |172.17.0.5:3000|False      |system_free_mem_pct  |28.89 %|    26.0 %|   90.0 %
stop-writes-count         |test     |testset|172.17.0.5:3000|False      |objects              |96.89 %|   9.689 K| 10.000 K
stop-writes-count         |test     |testset|172.17.0.3:3000|False      |objects              |97.08 %|   9.708 K| 10.000 K
stop-writes-count         |test     |testset|172.17.0.4:3000|False      |objects              |97.18 %|   9.718 K| 10.000 K
Number of rows: 24

udfs

The show udfs command displays user defined functions (UDF) modules as returned by the principal node.

Example: show udfs command output

Collectinfo-analyzer> show udfs
~~~~~~~~UDF Modules (2021-01-22 23:12:29 UTC)~~~~~~~~~
Filename|                                    Hash|Type
abc.123 |dceaf7f1acddf1d6e12a1752d499d80cfadfc24b|LUA
bar.lua |591d2536acb21a329040beabfd9bfaf110d35c18|LUA
foo.lua |f6eaf2b22d8b29b3597ef1ad9113d0907425ecd0|LUA

users

Access Control Permissions: user-admin

The show users [user] command displays users along with their associated roles as returned by the principal node. Optionally, you can display a single user by providing a username as the first argument.

Note

User runtime statistics were moved to the show users statistics command in asadm 2.15.0. From asadm 2.2.0 to asadm 2.14.0, runtime statistics were located in the show users table if quotas were enabled but only accounted for the principal node.

Example: show users command output

Collectinfo-analyzer> show users
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Users (2025-08-19 17:26:09 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                      To see individual users metrics run 'show users statistics USERNAME'
          User|                                                                 Roles|~Read~|~Write~|   Auth Mode
              |                                                                      | Quota|  Quota|
admin         |data-admin,read-write,read-write-udf,sindex-admin,sys-admin,user-admin|0     |0      |password,PKI
auditor_01    |                                                      readonly_auditor|100   |1      |password,PKI
backup_svc    |                                                       backup_operator|500   |500    |password,PKI
data_scientist|                                       analytics_user,readonly_auditor|0     |0      |password,PKI
devops_lead   |                                        app_developer,monitoring_agent|0     |0      |password,PKI
hft_bot       |                                                 high_frequency_trader|50000 |25000  |password,PKI
john_dev      |                                                         app_developer|5000  |2000   |password,PKI
prometheus    |                                                      monitoring_agent|1000  |1      |password,PKI
sarah_analyst |                                                        analytics_user|10000 |1      |password,PKI
Number of rows: 9

users statistics

Access Control Permissions: user-admin

The show users stat [user] command displays users, the number of user connections, and quota-related metrics across all nodes in the cluster. Use this to see the activity of users and find out which users might be close to or exceeding their assigned quotas. In addition to viewing users per node, there is also an additional aggregate line to display usage for the entire cluster. Optionally, you can retrieve a single user by providing a username as the first argument.

Example: users statistics command output

Collectinfo-analyzer> show users stat
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Users Statistics (2025-08-19 21:49:04 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     User|           Node|Connections|~~~~~~~~~~~~~~~~~~~~Read~~~~~~~~~~~~~~~~~~~|~~~~~~~~~~~~~~~~~~~Write~~~~~~~~~~~~~~~~~~~
         |               |           |   Quota|Usage%|   Single|  PI/SI|    PI/SI|   Quota|Usage%|   Single|  PI/SI|    PI/SI
         |               |           |        |      |   Record|  Query|    Query|        |      |   Record|  Query|    Query
         |               |           |        |      |      TPS|Limited|Limitless|        |      |      TPS|Limited|Limitless
         |               |           |        |      |         |    RPS|         |        |      |         |    RPS|
admin    |172.17.0.3:3000|    2.000  | 0.000  |    --|  0.000  |0.000  |  0.000  | 0.000  |    --|  0.000  |0.000  |  0.000
admin    |172.17.0.4:3000|    2.000  | 0.000  |    --|  0.000  |0.000  |  0.000  | 0.000  |    --|  0.000  |0.000  |  0.000
admin    |172.17.0.5:3000|    2.000  | 0.000  |    --|  0.000  |0.000  |  0.000  | 0.000  |    --|  0.000  |0.000  |  0.000
admin    |               |    6.000  | 0.000  | 0.0 %|  0.000  |0.000  |  0.000  | 0.000  | 0.0 %|  0.000  |0.000  |  0.000
reader   |172.17.0.3:3000|   13.000  |10.000 K|5.93 %|593.000  |0.000  |  0.000  | 1.000  | 0.0 %|  0.000  |0.000  |  0.000
reader   |172.17.0.4:3000|   13.000  |10.000 K|5.15 %|515.000  |0.000  |  0.000  | 1.000  | 0.0 %|  0.000  |0.000  |  0.000
reader   |172.17.0.5:3000|   13.000  |10.000 K| 4.7.0 %|470.000  |0.000  |  0.000  | 1.000  | 0.0 %|  0.000  |0.000  |  0.000
reader   |               |   39.000  |30.000 K|5.26 %|  1.578 K|0.000  |  0.000  | 3.000  | 0.0 %|  0.000  |0.000  |  0.000
root     |172.17.0.3:3000|         --| 0.000  |    --|  0.000  |0.000  |  0.000  | 0.000  |    --|  0.000  |0.000  |  0.000
root     |172.17.0.4:3000|         --| 0.000  |    --|  0.000  |0.000  |  0.000  | 0.000  |    --|  0.000  |0.000  |  0.000
root     |172.17.0.5:3000|         --| 0.000  |    --|  0.000  |0.000  |  0.000  | 0.000  |    --|  0.000  |0.000  |  0.000
root     |               |         --| 0.000  | 0.0 %|  0.000  |0.000  |  0.000  | 0.000  | 0.0 %|  0.000  |0.000  |  0.000
superuser|172.17.0.3:3000|   14.000  | 0.000  |    --|263.000  |0.000  |  0.000  | 0.000  |    --|271.000  |0.000  |  0.000
superuser|172.17.0.4:3000|   12.000  | 0.000  |    --|225.000  |0.000  |  0.000  | 0.000  |    --|257.000  |0.000  |  0.000
superuser|172.17.0.5:3000|   14.000  | 0.000  |    --|227.000  |0.000  |  0.000  | 0.000  |    --|226.000  |0.000  |  0.000
superuser|               |   40.000  | 0.000  | 0.0 %|715.000  |0.000  |  0.000  | 0.000  | 0.0 %|754.000  |0.000  |  0.000
writer   |172.17.0.3:3000|   14.000  | 1.000  | 0.0 %|  0.000  |0.000  |  0.000  |10.000 K|5.29 %|529.000  |0.000  |  0.000
writer   |172.17.0.4:3000|   12.000  | 1.000  | 0.0 %|  0.000  |0.000  |  0.000  |10.000 K|4.56 %|456.000  |0.000  |  0.000
writer   |172.17.0.5:3000|   14.000  | 1.000  | 0.0 %|  0.000  |0.000  |  0.000  |10.000 K|4.45 %|445.000  |0.000  |  0.000
writer   |               |   40.000  | 3.000  | 0.0 %|  0.000  |0.000  |  0.000  |30.000 K|4.77 %|  1.430 K|0.000  |  0.000
Number of rows: 15

summary

The summary command summarizes cluster data from a collectinfo archive. Add -l for the numbered list view (summary -l).

If the cluster unique data was counted with Aerospike Unique Data Agent when the collectinfo was created using --agent-host and --agent-port, you may optionally use the --agent-unstable flag to include values in the Usage (Unique Data) value where the cluster was reportedly unstable.

Note

Aerospike Tools 7.1.1 or later is required to use asadm integration with UDA.

Memory and index lines (Tools 13.0.2 / asadm 5.0.2 and later)

In Tools 13.0.2 and later, summary -l reports index memory and data storage on separate lines. Data Memory, Data Device, and Data Pmem count record storage only; Shmem Sindex, Pmem Sindex, Flash Sindex, and Set Index show index RAM separately. See summary in live cluster mode for the full line reference.

Example: summary -l with shmem indexes (collectinfo analyzer)

Collectinfo-analyzer> summary -l
Cluster
=======

   1.   Cluster Name             :  bob-cluster-a
   2.   Server Version           :  E-8.2.0.0-45
   3.   OS Version               :  Ubuntu 22.04.4 LTS (5.15.0-140-generic)
   4.   Cluster Size             :  3
   5.   Devices                  :  Total 0, per-node 0
   6.   System Memory            :  74.00% free
   7.   Shmem Index              :  12.207 MB used
   8.   Shmem Sindex             :  480.000 MB used
   9.   Set Index                :  3.052 MB used
   10.  Data Memory              :  Total 6.000 GB, 0.36% used (22.411 MB), 90.00% available contiguous space (5.400 GB)
   11.  License Usage            :  Latest: (11.206 MB) ?
   12.  Active Namespaces        :  1 of 1
   13.  Active Features          :  Batch, Index-on-shmem, KVS, PIndex Query


Namespaces
==========

   test
   ====
   1.   Devices                  :  Total 0, per-node 0
   2.   Shmem Index              :  12.207 MB used
   3.   Shmem Sindex             :  480.000 MB used
   4.   Set Index                :  3.052 MB used
   5.   Data Memory              :  Total 6.000 GB, 0.36% used (22.411 MB), 90.00% available contiguous space (5.400 GB)
   6.   License Usage            :  Latest: (11.206 MB) ?
   7.   Replication Factor       :  2
   8.   Rack-aware               :  False
   9.   Master Objects           :  100.001 K
   10.  Compression-ratio        :  1.0

Note

Starting in asadm 4.1.0 and tools package 12.1.0, if asdb-compression is true in the Aerospike feature key file, the summary command includes a warning to indicate that the license usage calculation is inaccurate.