From 56e0ac989d9f7c9f37deabef991e1522724a724c Mon Sep 17 00:00:00 2001 From: Lucien Volmar Date: Thu, 21 Apr 2016 16:13:37 -0700 Subject: [PATCH] Aerospike Telemetry Notice --- aerospike/content.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/aerospike/content.md b/aerospike/content.md index 928918819..325fdcc60 100644 --- a/aerospike/content.md +++ b/aerospike/content.md @@ -77,7 +77,4 @@ For more details and examples of clustering Aerospike in Docker, please see [Dep ## 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/) +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/)