From a1da73a38a995c22dae39375811d9dbf677f5473 Mon Sep 17 00:00:00 2001 From: Lucien Volmar Date: Thu, 21 Apr 2016 16:09:25 -0700 Subject: [PATCH] Aerospike Telemetry notice --- aerospike/content.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/aerospike/content.md b/aerospike/content.md index 73e6ede0..92891881 100644 --- a/aerospike/content.md +++ b/aerospike/content.md @@ -74,3 +74,10 @@ Mesh networking requires setting up links between each node in the cluster. This 2. Use `asinfo` to send the `tip` command, to make the node aware of another node, as defined in [tip command in asinfo](http://www.aerospike.com/docs/tools/asinfo/#tip). For more details and examples of clustering Aerospike in Docker, please see [Deploying Aerospike clusters with Docker](http://www.aerospike.com/docs/deploy_guides/docker/). + +## Sending Performance Data to Aerospike + +Aerospike Telemetry is a feature that allows us to collect certain use data – not the database data – on your Aerospike Community Edition server use. +We'd like to know when clusters are created and destroyed, cluster size, cluster workload, how often queries are run, whether instances are deployed purely in-memory or with Flash. +Aerospike Telemetry collects information from running Community Edition server instances every 10 minutes. The data helps us to understand how the product is being used, +identify issues, and create a better experience for the end user. [More Info](http://www.aerospike.com/aerospike-telemetry/)