Excluding keyspaces and tables from data collection

By default, OpsCenter does not collect performance data for its own keyspace or the Cassandra system keyspace. You can manually add any other keyspaces or tables that you do not want to monitor in the [cassandra_metrics] section of the cluster_name.conf configuration file.

By default, OpsCenter does not collect performance data for its own keyspace or the Cassandra system keyspace. You can manually add any other keyspaces or tables that you do not want to monitor in the [cassandra_metrics] section of the cluster_name.conf configuration file. For example, to prevent data collection for the keyspace test as well as the table Keyspace1.Standard1, update the OpsCenter cluster configuration cluster_name.conf file. The location of this file depends on the type of installation:

  • Package installations: /etc/opscenter/clusters/cluster_name.conf

  • Tarball installations: install_location/conf/clusters/cluster_name.conf

Uncomment and edit the following values in cluster_name.conf:

[cassandra_metrics]
ignored_keyspaces = system, OpsCenter, test
ignored_column_families = Keyspace1.Standard1

Tables (formerly column families) are specified in the format:

<keyspace_name>.<column_family_name>.

Configuration properties still refer to tables as column families in OpsCenter.

Metrics Collection Properties

  • [cassandra_metrics] ignored_keyspaces

    A list of keyspaces to not collect metrics for, separated by commas. The default value is system, system_traces, system_auth, dse_auth, OpsCenter, system_views and system_virtual_schema.

  • [cassandra_metrics] ignored_column_families

    A list of tables to not collect metrics for, separated by commas. Each entry should be of the form "ks.cf". For example: metrics_ignored_column_families = system.NodeInfo, system.Schema, Keyspace1.Standard1

  • [cassandra_metrics] ignored_solr_cores

    A list of solr cores to not collect metrics for, separated by commas. Each entry should be of the form "ks.cf". For example: metrics_ignored_solr_cores = Keyspace1.Standard1, solr.wiki.

These properties set the expiration time for data stored in the OpsCenter keyspace. Each time period for rolling up data points into summary views has a separate expiration threshold, or time-to-live (ttl) value expressed in seconds. By default, shorter time periods have lower values that result in more efficient expiration and compaction of the relatively larger volumes of data. Uncomment these properties to change the default expiration periods for performance data. Properties and default values are:

  • [cassandra_metrics] 1min_ttl

    Sets the time in seconds to expire 1 minute data points. The default value is 604800 (7 days).

  • [cassandra_metrics] 5min_ttl

    Sets the time in seconds to expire 5 minute data points. The default value is 2419200 (28 days).

  • [cassandra_metrics] 2hr_ttl

    Sets the time in seconds to expire 2 hour data points. The default value is 31536000 (365 days).

  • [cassandra_metrics] 24hr_ttl

    Sets the time to expire 24 hour data points. The default value is 0, or never.

Rollup tables

OpsCenter rollup tables store the metrics that are displayed in the OpsCenter monitoring graphs. Each rollup table collects data for the period identified in the rollup table. For example, rollups60 stores an average or aggregate data point for a 60-second period.

The rollup tables are stored within the OpsCenter keyspace in the OpsCenter keyspace on the monitored DataStax Enterprise (DSE) cluster or a separate OpsCenter storage cluster.

Configure time-to-live (TTL) value for the collected data to remain in each rollup table in the [agent_config] section of cluster_name.conf.

  • [rollup_state_ttl] The time-to-live (TTL) for data points stored in rollup states before data is collected in the rollup60 table. Default: (* 86400 3) Example: rollup_state_ttl: 259200

  • [rollups60_ttl] Sets time-to-live (TTL) for rollups60 in seconds. A value of '0' prevents the data from expiring. Setting '-1' disables this rollup and prevents storing any data for it which might help reduce used disk space. Default: 604800 Example: rollups60_ttl: 604800

  • [rollups300_ttl] Sets time-to-live (TTL) for rollups300 in seconds. A value of '0' prevents the data from expiring. Setting '-1' disables this rollup and prevents storing any data for it which might help reduce used disk space. Default: 604800 Example: rollups300_ttl: 2419200

  • [rollups7200_ttl] Sets time-to-live (TTL) for rollups7200 in seconds. A value of '0' prevents the data from expiring. Setting '-1' disables this rollup and prevents storing any data for it which might help reduce used disk space. Default: 31536000 Example: rollups7200_ttl: 31536000

  • [rollups86400_ttl] Sets time-to-live (TTL) for rollups86400 in seconds. A value of '0' prevents the data from expiring. Setting '-1' disables this rollup and prevents storing any data for it which might help reduce used disk space. Default: 0 Example: rollups86400_ttl: 0

Related information

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, info@datastax.com