Configuration files for OpsCenter

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

• opscenterd.conf: configures 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 DataStax 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 DataStax 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 DataStax Agents. Setting DataStax 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 [agent_config] section of cluster_name.conf on the opscenterd machine and the properties propagate automatically to all DataStax 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

Settings in address.yaml take precedence over settings in cluster_name.conf. Therefore, 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, review the Upgrade Guide.