Aerospike

The Aerospike integration collects key namespace and system metrics, such as disk and memory usage, scans, and connections. The integration collects these metrics using the official client API provided by Aerospike.

For more information about Aerospike, see the Aerospike documentation.

Prerequisites

To collect Aerospike telemetry, you must install the Ops Agent version 2.18.2 or higher.

This integration supports Aerospike versions 4.9, 5.x, and 6.x.

Configure the Ops Agent for Aerospike

Following the guide for Configuring the Ops Agent, add the required elements to collect telemetry from Aerospike instances, and restart the agent.

Example configuration

The following command creates the configuration to collect and ingest telemetry for Aerospike and restarts the Ops Agent.

# Configures Ops Agent to collect telemetry from the app and restart Ops Agent.

set -e

sudo tee /etc/google-cloud-ops-agent/config.yaml > /dev/null << EOF
metrics:
  receivers:
    aerospike:
      type: aerospike
  service:
    pipelines:
      aerospike:
        receivers:
          - aerospike
EOF

sudo service google-cloud-ops-agent restart
sleep 30

Configure metrics collection

To ingest metrics from Aerospike, you must create receivers for the metrics that Aerospike produces and then create a pipeline for the new receivers.

To configure a receiver for your aerospike metrics, specify the following fields:

Field Default Description
collect_cluster_metrics true Configures the receiver to collect metrics from peer nodes of the Aerospike system.
collection_interval 60s A time.Duration value, such as 30s or 5m.
endpoint localhost:3000 Address of the Aerospike system, formatted as host:port.
password The configured password if Aerospike is configured to require authentication.
timeout 20s Timeout for requests to the Aerospike system, a time.Duration value such as 30s or 5m.
type aerospike This value must be aerospike.
username The configured username if Aerospike is configured to require authentication.

What is monitored

The following table provides the list of metrics that the Ops Agent collects from the Aerospike instance.

Metric type 
Kind, Type
Monitored resources
Labels
workload.googleapis.com/aerospike.namespace.disk.available
GAUGEINT64
gce_instance
node_name
namespace_name
workload.googleapis.com/aerospike.namespace.memory.free
GAUGEINT64
gce_instance
node_name
namespace_name
workload.googleapis.com/aerospike.namespace.memory.usage
GAUGEINT64
gce_instance
component
node_name
namespace_name
workload.googleapis.com/aerospike.namespace.scan.count
CUMULATIVEINT64
gce_instance
result
type
node_name
namespace_name
workload.googleapis.com/aerospike.namespace.transaction.count
CUMULATIVEINT64
gce_instance
result
type
node_name
namespace_name
workload.googleapis.com/aerospike.node.connection.count
CUMULATIVEINT64
gce_instance
operation
type
node_name
workload.googleapis.com/aerospike.node.connection.open
GAUGEINT64
gce_instance
type
node_name
workload.googleapis.com/aerospike.node.memory.free
GAUGEINT64
gce_instance
node_name

Sample dashboard

To view your Aerospike metrics, you must have a chart or dashboard configured. Cloud Monitoring provides a library of sample dashboards for integrations, which contain preconfigured charts. For information about installing these dashboards, see Installing sample dashboards.

Verify the configuration

This section describes how to verify that you correctly configured the Aerospike receiver. It might take one or two minutes for the Ops Agent to begin collecting telemetry.

To verify that the metrics are ingested, go to Metrics Explorer and run the following query in the MQL tab:

fetch gce_instance
| metric 'workload.googleapis.com/aerospike.node.connection.open'
| every 1m

What's next

For a walkthrough on how to use Ansible to install the Ops Agent, configure a third-party application, and install a sample dashboard, see the Install the Ops Agent to troubleshoot third-party applications video.