Configuration files for OpsCenter

Configure capabilities by manually modifying the opscenterd.conf, cluster_name.conf, and address.yaml configuration files.

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

logback.xml

The location of the logback.xml file depends on the type of installation:

Package installations
Installer-Services installations

/etc/dse/cassandra/logback.xml

Tarball installations
Installer-No Services installations

installation_location/resources/cassandra/conf/logback.xml
  • The logback.xml file is located in the installation_location/conf directory.

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

address.yaml

The location of the address.yaml file depends on the type of installation:
  • Package installations: /var/lib/datastax-agent/conf/address.yaml
  • Tarball installations: install_location/conf/address.yaml

Configure capabilities by manually modifying the opscenterd.conf, cluster_name.conf, and address.yaml configuration files.

Note: The OpsCenter console is the most convenient way to configure basic OpsCenter connection settings for authentication and encryption.
  • opscenterd.conf: configures the properties of the OpsCenter daemon.
  • cluster_name.conf: configures properties for each cluster monitored by OpsCenter. OpsCenter creates the cluster_name.conf file named the same as the cluster when a cluster is added to OpsCenter.
    Tip: You can set most of the agent configuration options in the [agent_config] section of the cluster_name.conf file. The options in the [agent_config] section must match the corresponding configuration option name in address.yaml. Setting agent options through the cluster configuration file sets the corresponding property in address.yaml on every node. Some properties or some cases might require setting these properties directly in address.yaml on applicable agents. Setting agent configuration options that require a list entry (value1,value2,value3 and so forth) is not supported in cluster_name.conf.
  • address.yaml: configures the properties for the DataStax agent. Setting options in address.yaml must be done for every node. You can set most of these properties in the [agents] section of cluster_name.conf on the opscenterd machine and the properties propagate automatically to all agents.
  • logback.xml: configures the logging properties for the OpsCenter daemon. This includes HTTP request logging, cluster logging, and security logging.

Precedence for OpsCenter configuration files

In versions of OpsCenter prior to 5.2, the settings in the cluster_name.conf configuration file took precedence over settings in address.yaml. In OpsCenter version 5.2 and going forward, the reverse is true: address.yaml settings take precedence over cluster_name.conf. To summarize, OpsCenter 5.2 and later configuration files precedence, settings in address.yaml override settings in cluster_name.conf, which in turn override default configuration settings.

Changes to configuration options

To keep current on changes to available configuration options with each release, be sure to review the Upgrade Guide.