Best Practice Service

The Best Practice service periodically scans clusters to automatically detect issues that affect a cluster’s health. It includes a set of rules organized into categories that are used to analyze the nodes in a cluster and report back any deviations from the best practice recommendations. The status dialog for each rule includes recommendations for fixing any problems. See Monitoring the results of Best Practice service scans.

The Best Practice Service is enabled by default and cannot be disabled in its entirety. Individual rules can be turned on or off as appropriate for an environment. The status summary of passing or failing active rules is shown on the main Services page in the Status column. Best Practice Service Status Services Page

Also by default, the majority of best practice rules are enabled (with the exception of the Sensitive Config Value Encryption rule in the Security Advisor) and configured to run at 5:00 AM GMT. Configure which rules to run on a schedule appropriate for your organization.

If a best practice rule fails, it sends an alert. Similar to other alerts, you can configure notification settings for these rules.

OpsCenter stores the results of a Best Practice Service run for four weeks by default. Use the [bestpractice] results_ttl to configure the time-to-live value of Best Practice results scans.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,