Aerospike Telemetry notice
This commit is contained in:
parent
7c46bca52d
commit
a1da73a38a
|
|
@ -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/)
|
||||
|
|
|
|||
Loading…
Reference in New Issue