Storing collection data on a different cluster

Store collection data on a separate DSE cluster as an alternative to OpsCenter storing data in an OpsCenter keyspace on the DSE cluster being managed. Storing data in a separate storage cluster is an enterprise-only feature.

cluster_name.conf 

The location of the cluster_name.conf file depends on the type of installation:

  • Package installations: /etc/opscenter/clusters/cluster_name.conf
  • Tarball installations: install_location/conf/clusters/cluster_name.conf
  • Windows installations: Program Files (x86)\DataStax Community\opscenter\conf\clusters\cluster_name.conf

If you do not want OpsCenter to store data in an OpsCenter keyspace on the DSE cluster being managed, you can store the data on a separate DSE cluster. Storing data in a separate storage cluster is an enterprise-only feature. The seed nodes must be accessible without SSL or Kerberos security.

A unique keyspace must be used for each DSE cluster being managed by OpsCenter. If you are storing data for multiple clusters, we recommend adding the cluster name as a suffix to the default keyspace name of OpsCenter. For example, set the keyspace name to OpsCenter_Cluster1.

Procedure

Add a section to the cluster configuration file, cluster_name.conf. 

[storage_cassandra]
seed_hosts = host1, host2
api_port = 9160
keyspace = OpsCenter_Cluster1
Option Description
seed_hosts A comma-delimited list of at least one of the nodes in the DSE cluster where you want to store collection data.
api_port The Thrift port used by that DSE cluster.
username The appropriate username (if using Thrift security).
password The appropriate password (if using Thrift security).
keyspace The name of the keyspace to store the collection data in. (OpsCenter by default.)