Documentationbreadcrumb arrow Grafana Cloudbreadcrumb arrow Observe and actbreadcrumb arrow Monitor infrastructurebreadcrumb arrow Grafana integrationsbreadcrumb arrow Integrations referencebreadcrumb arrow Aerospike
Grafana Cloud

Aerospike integration for Grafana Cloud

Aerospike is a high-performance, NoSQL, key-value database designed for ultra-low-latency and high-throughput applications. It offers fast data storage and retrieval, scalability, and ACID compliance, making it suitable for real-time, mission-critical data processing.

This integration supports Aerospike 6.2.0 or later.

This integration includes 8 useful alerts and 4 pre-built dashboards to help monitor and visualize Aerospike metrics and logs.

Before you begin

Aerospike

This integration is designed to target clustered Aerospike environments. For best results, namespaces within a single cluster should have unique names.

By default, Aerospike logs to STDERR. To enable log collection for your Aerospike instance, create the /var/log/aerospike directory and modify the logging section of the instance’s aerospike.conf file to send logs to a file. Save these changes and restart Aerospike to begin logging to a file.

  • context any instructs Aerospike to capture log messages from all contexts. For a full list of logging contexts, refer to Log management in the Aerospike documentation.
  • info instructs Aerospike to capture log messages of severity level info or higher. Other possible values are critical, warning, debug, and detail.

This example is the recommended configuration for an Aerospike instance, but if your log file path or name differs, modify your configuration accordingly.

logging {
        file /var/log/aerospike/aerospike.log {
                context any info
        }
}

Certain metrics used in this integration may not appear depending on your Aerospike instance’s configuration (aerospike.conf):

  • To monitor disk metrics, configure one or more namespaces to use storage-engine device.
  • To monitor cache metrics, configure one or more namespaces to use storage-engine device with data-in-memory false.

Example namespace configuration:

namespace test {
        replication-factor 2
        memory-size 1G

        storage-engine device {
                file /opt/aerospike/data/test.data
                filesize 1G
                data-in-memory false
                read-page-cache true
        }
}

Aerospike Prometheus Exporter

This integration supports metrics and logs from an Aerospike instance. It works with the Aerospike Prometheus Exporter, which you install and configure separately from Grafana Alloy.

Install Aerospike integration for Grafana Cloud

  1. In your Grafana Cloud stack, click Connections in the left-hand menu.
  2. Find Aerospike and click its tile to open the integration.
  3. Review the prerequisites in the Configuration Details tab and set up Grafana Alloy to send Aerospike metrics and logs to your Grafana Cloud instance.
  4. Click Install to add this integration’s pre-built dashboards and alerts to your Grafana Cloud instance, and you can start monitoring your Aerospike setup.

Configuration snippets for Grafana Alloy

Advanced mode

The following snippets provide examples to guide you through the configuration process.

To instruct Alloy to scrape your Aerospike instances, manually copy and append the snippets to your Alloy configuration file, then follow subsequent instructions.

Advanced metrics snippets

Alloy 
prometheus.scrape "metrics_integrations_integrations_aerospike" {
	targets = [{
		__address__       = "<node-hostname>:9145",
		aerospike_cluster = "<as-cluster-name>",
	}]
	forward_to = [prometheus.remote_write.metrics_service.receiver]
	job_name   = "integrations/aerospike"
}

To monitor your Aerospike instance, use a prometheus.scrape component to scrape the Aerospike Prometheus Exporter.

Configure the following properties for each target in the targets list:

  • __address__: The address of the Aerospike Prometheus Exporter metrics endpoint. Replace <node-hostname> with the hostname of the Aerospike node. The exporter listens on port 9145 by default. The instance label is set to this address.
  • aerospike_cluster: The aerospike_cluster label to group your Aerospike instances within a cluster. Set the same value for all nodes within your cluster.

If you have multiple Aerospike nodes to scrape, add a target for each one to the targets list.

Advanced logs snippets

linux

Alloy 
local.file_match "logs_integrations_integrations_aerospike" {
	path_targets = [{
		__address__       = "localhost",
		__path__          = "/var/log/aerospike/aerospike.log",
		aerospike_cluster = "<as-cluster-name>",
		instance          = "<node-hostname>:9145",
		job               = "integrations/aerospike",
	}]
}

loki.process "logs_integrations_integrations_aerospike" {
	forward_to = [loki.write.grafana_cloud_loki.receiver]

	stage.multiline {
		firstline     = "\\w{3} \\d{2} \\d{4}"
		max_lines     = 0
		max_wait_time = "3s"
	}

	stage.regex {
		expression = "\\w{3} \\d{2} \\d{4} \\d{2}:\\d{2}:\\d{2} \\w{3}: (?P<level>\\w+) \\((?P<context>\\w+)\\): (?P<trace>\\(\\S+\\))\\s+(?P<message>(?s:.*))$"
	}

	stage.labels {
		values = {
			context = null,
			level   = null,
		}
	}
}

loki.source.file "logs_integrations_integrations_aerospike" {
	targets    = local.file_match.logs_integrations_integrations_aerospike.targets
	forward_to = [loki.process.logs_integrations_integrations_aerospike.receiver]
}

To monitor your Aerospike instance logs, use a combination of the following components:

  • local.file_match defines where to find the log file to be scraped. Change the following properties according to your environment:

    • __address__: The Aerospike instance address
    • __path__: The path to the log file.
    • instance label: Set it to the same value as the metrics target’s __address__, for example <node-hostname>:9145, so that the logs and metrics for this node have the same instance label.
    • aerospike_cluster: The aerospike_cluster label to group your Aerospike instances within a cluster. Set the same value for all nodes within your cluster.

  • loki.process defines how to process logs before sending them to Grafana Loki.

  • loki.source.file sends logs to Loki.

Kubernetes instructions

Dashboards

The Aerospike integration installs the following dashboards in your Grafana Cloud instance to help monitor your system.

  • Aerospike instance overview
  • Aerospike logs
  • Aerospike namespace overview
  • Aerospike overview

Aerospike overview (cluster overview)

Aerospike overview (cluster overview)

Aerospike overview (client requests)

Aerospike overview (client requests)

Aerospike logs (logs)

Aerospike logs (logs)

Alerts

The Aerospike integration includes the following useful alerts:

AlertDescription
AerospikeNodeHighMemoryUsageCritical: There is a limited amount of memory available for a node.
AerospikeNamespaceHighDiskUsageCritical: There is a limited amount of disk space available for a node.
AerospikeUnavailablePartitionsCritical: There are unavailable partitions in the Aerospike cluster.
AerospikeDeadPartitionsCritical: There are dead partitions in the Aerospike cluster.
AerospikeNamespaceRejectingWritesCritical: A namespace is currently rejecting all writes. Check for unavailable/dead partitions, clock skew, or nodes running out of memory/disk.
AerospikeHighClientReadErrorRateWarning: There is a high rate of errors for client read transactions.
AerospikeHighClientWriteErrorRateWarning: There is a high rate of errors for client write transactions.
AerospikeHighClientUDFErrorRateWarning: There is a high rate of errors for client UDF transactions.

Metrics

The most important metrics provided by the Aerospike integration, which are used on the pre-built dashboards and Prometheus alerts, are as follows:

  • aerospike_namespace_cache_read_pct
  • aerospike_namespace_client_read_error
  • aerospike_namespace_client_read_filtered_out
  • aerospike_namespace_client_read_not_found
  • aerospike_namespace_client_read_success
  • aerospike_namespace_client_read_timeout
  • aerospike_namespace_client_udf_complete
  • aerospike_namespace_client_udf_error
  • aerospike_namespace_client_udf_filtered_out
  • aerospike_namespace_client_udf_timeout
  • aerospike_namespace_client_write_error
  • aerospike_namespace_client_write_filtered_out
  • aerospike_namespace_client_write_success
  • aerospike_namespace_client_write_timeout
  • aerospike_namespace_clock_skew_stop_writes
  • aerospike_namespace_data_used_pct
  • aerospike_namespace_dead_partitions
  • aerospike_namespace_device_free_pct
  • aerospike_namespace_memory_free_pct
  • aerospike_namespace_ns_cluster_size
  • aerospike_namespace_stop_writes
  • aerospike_namespace_unavailable_partitions
  • aerospike_node_stats_client_connections
  • aerospike_node_stats_fabric_connections
  • aerospike_node_stats_heap_efficiency_pct
  • aerospike_node_stats_heartbeat_connections
  • aerospike_node_stats_system_free_mem_pct
  • up

Changelog

md 
# 1.1.2 - October 2026

- Fix the Kubernetes logs snippet so that it loads: remove extra escaping from the selector and regexes
- Docs: Remove the `ape.toml` logging step, which configures the exporter's own log file, and match the advanced metrics and logs instructions to the snippets

# 1.1.1 - June 2026

- Fixed issue with default filtering selectors

# 1.1.0 - June 2026

- Updated dashboards to follow new stylistic standards

# 1.0.0 - December 2025

* Chore: Fix incorrect semver to 1.0.0. No further changes

# 0.0.2 - November 2024

- Update status panel check queries

# 0.0.1 - September 2023

- Initial release

Cost

By connecting your Aerospike instance to Grafana Cloud, you might incur charges. To view information on the number of active series that your Grafana Cloud account uses for metrics included in each Cloud tier, see Active series and dpm usage and Cloud tier pricing.