Aerospike Database metrics

Every Aerospike Cloud database cluster exposes metrics from each cluster node. Aerospike Cloud runs Aerospike Prometheus Exporter alongside each cluster node. Aerospike Prometheus Exporter collects metrics from each cluster node and exports those metrics on port 9145 at the same database hostname as the Aerospike database.

To learn more about Aerospike Prometheus Exporter and the Aerospike monitoring stack, see Monitoring stack components.

Collect Aerospike metrics

Use the following steps to collect metrics from Aerospike Cloud database clusters.

Get the Aerospike Cloud database hostname from the Aerospike Cloud Console.
(optional) Run the following command to verify that metrics can be collected:

Reminder
Running this command is only intended as a test. The command must be run over the VPC peering connection, and only returns metrics from the first node it resolves.
Terminal window
```
curl <database-hostname>:9145/metrics
```
For example, if the database hostname is 0ecf039f-4abe-472d-aaf9-d99e55aa9f3a.aerospike.internal:
Terminal window
```
curl 0ecf039f-4abe-472d-aaf9-d99e55aa9f3a.aerospike.internal:9145/metrics
```
The command returns a list of Aerospike metrics in Prometheus metric format. See the Metrics Reference for a full list of available metrics.
Configure a Prometheus server to collect metrics from the database hostname on port 9145 and path /metrics.

The database hostname resolves to an A record for each Aerospike node, meaning the database hostname returns many host targets. When collecting metrics with Prometheus, use the dns_sd_config scrape configuration. For more information, see the Prometheus documentation.
Terminal window
```
# prometheus config file
scrape_configs:
- job_name: aerospike
    metrics_path: /metrics
    scheme: http
    scrape_interval: 30s
    dns_sd_configs:
    - names:
      DATABASE_HOSTNAME
      type: A
      port: 9145
```