Statistics reporter properties
A complete breakdown of the data OpsCenter communicates back to DataStax. The data is sent in a key-value JSON format.
opscenterd.conf
The location of the opscenterd.conf file depends on the type of installation:- Package installations: /etc/opscenter/opscenterd.conf
- Tarball installations: install_location/conf/opscenterd.conf
OpsCenter communicates data about an installed instance back to DataStax for informational purposes. The data is sent in a key-value JSON format.
If your organization prefers disabling transmission of the collected data to DataStax, add the
following in opscenterd.conf and restart
OpsCenter:
[stat_reporter] interval=0
The following information is recorded about the OpsCenter install:
- install_id
- This is a random uuid generated when OpsCenter starts for the first time. This is used for associating reports from the same install.
- is_paid
- This is a flag indicating whether or not this is the
free
orenterprise
version of OpsCenter. - opscenter_version
- The version of OpsCenter in use.
- opscenter_ram
- The amount of RAM, in megabytes, on the OpsCenter machine.
- opscenter_cores
- The number of cores on the OpsCenter machine.
- opscenter_os
- The generic name of the operating system of the OpsCenter machine. For example,
linux
ormac
. - opscenter_os_sub
- The specific name of the operating system of the OpsCenter machine. For example
CentOS
,Ubuntu
, orDebian
. - opscenter_os_version
- The operating system version of the OpsCenter machine.
- opscenter_arch
- The architecture of the OpsCenter machine.
- opscenter_install_type
- The type of install (package or tarball).
- python_version
- The version of python running on the OpsCenter machine.
- opscenter_instance_type
- The instance type the OpsCenter machine, if OpsCenter is running in EC2.
- separate_storage
- A flag indicating if OpsCenter is storing metrics in the cluster it is monitoring.
- config_diff
- A list of the OpsCenter config options that were modified to be different than the defaults. This includes the names of the options that were changed but not the values of those options.
These statistics are collected about each cluster OpsCenter is monitoring:
- cluster_id
- An MD5 hash of the cluster name. Used for identifying unique clusters while maintaining anonymity.
- conf_id
- An MD5 hash of the file name the config for the cluster is stored in. Used for the same purposes as cluster_id.
- partitioner
- The partitioner the cluster is using.
- snitch
- The snitch the cluster is using.
- keyspace_count
- The number of keyspaces in the cluster.
- columnfamily_count
- The number of column families in the cluster.
- strategy_options
- A list of the replication options used for each keyspace in the cluster.
- cql3_cf_count
- The number of column families created with CQL3 in the cluster.
- node_count
- The number of nodes in the cluster.
- avg_token_count
- The average number of tokens per node.
- bdp_version
- A list of the different DataStax Enterprise versions in the cluster.
- rack_map
- A map of each rack in the cluster and how many nodes are in that rack.
- dc_count
- The number of data centers in the cluster.
- free_space
- The amount of free disk space across the cluster.
- used_space
- The amount of used disk space across the cluster.
- cluster_os
- A list of the different operating systems used across the cluster.
- cluster_ram
- The average amount of ram per node in the cluster.
- cluster_cores
- The average number of cores per node in the cluster.
- cluster_instance_types
- A list of the EC2 instance types in the cluster, if EC2 is being used.