HOME
ACADEMY
DOCS
CONTACT US
DOWNLOAD DATASTAX
GLOSSARY
SUPPORT
DEVELOPER BLOGS
This document is
no longer maintained
.
OpsCenter 4.1 User Guide
(Not supported)
About OpsCenter
Key features
Installation
Installing OpsCenter
Installing the OpsCenter RPM package
Installing the OpsCenter deb package
Installing on Mac OS X or any Linux distribution
Installing DataStax agents
Manually deploying agents - tarball
Manually deploying agents - rpm
Manually deploying agents - deb
Automatic installation of DataStax agents
Configuring JAVA_HOME for DataStax agents
OpsCenter and DataStax agent ports
Installation and configuration locations
Debian and Ubuntu Package install locations
CentOS, OEL, and RHEL Package install locations
Binary Tarball distribution install locations
Starting, restarting, and stopping OpsCenter
Starting and restarting DataStax agents
Upgrading OpsCenter
Configuration
Configuring user access
About user access roles
Assigning or modifying user access roles
Removing a user
Configuring SSL
Enabling SSL - package installations
Enabling SSL - tarball installations
Disabling SSL - package installations
Disabling SSL - tarball installations
Enabling HTTPS
Configuring events and alerts
Enabling email alerts
Enabling alerts posted to a URL
Verifying that events are posting correctly
Configuring data collection and expiration
Estimating the amount of data generated
Controlling data collection
Storing collection data on a different cluster
Configuring OpsCenter definition file updates
Advanced configuration
OpsCenter configuration properties
Cluster configuration properties
DataStax Agent configuration
OpsCenter updater properties
Backing up opscenterd's configuration files for failover
Using custom start/stop scripts for DataStax Enterprise and Cassandra
Example scenarios
Configuring for multiple regions
Using OpsCenter
Overview
Managing clusters
Creating a cluster
Adding an existing cluster
Node monitoring and administration
Ring View
List View
Node management operations
Cluster administration
Generating a report
Collecting diagnostic data
Adding a node to a cluster
Configuring a cluster
Removing a cluster
Rebalancing a cluster
Restarting a cluster
Modifying a cluster setting
Performance metrics
Using performance metrics
Cluster performance metrics
Pending task metrics
Alert metrics
Advanced system alert metrics
Managing DataStax Enterprise Management Services
Repair Service
Capacity Service
Managing backups and restoring from backups
Scheduling a backup
Restoring from a backup
Using custom scripts before and after backups
Data modeling
Keyspaces
Managing column families
Browsing data
Troubleshooting
Internet Explorer web browser not supported
The SSTables in this snapshot '<tag>' are not compatible
OpsCenter data growing too large
Cannot create a keyspace
Error exceptions.ImportError:libssl.so.0.9.8
Python used to run OpsCenter not built with SSL
DataStax agent port setting conflict
Limiting the metrics collected by OpsCenter
Java not installed or JAVA_HOME environment variable not set
Insufficient user resource limits errors
Installing EPEL on CentOS 5.x or RHEL 5.x
Problems with provisioning
General troubleshooting steps
Invalid repository credentials
Timed out waiting for Cassandra to start
The following packages are already installed
Agents cannot connect to opscenterd
Removing all Cassandra or DSE files after failed provisioning
Running sstableloader results in broken data distribution
Timeout connecting to Cassandra 2.0 clusters
Sophos Web Protection breaks browser access to OpsCenter on Windows
OpsCenter API reference
Release Notes
4.1.4
4.1.3
4.1.2
4.1.1
4.1.0
4.0.3
4.0.2
4.0.1
4.0
Feedback
Home
Academy
Docs home
Contact us
Download DataStax
Glossary
Support
Developer blogs
Search
Home
Configuration
Configuration
How to configure OpsCenter.
Configuring user access
By default, access control is disabled. Any user that knows the OpsCenter URL can view all objects and perform all tasks. To control access, you configure authentication for OpsCenter users by performing these tasks:
Configuring SSL
OpsCenter uses Secure Socket Layer (SSL) to encrypt the communication protocol and authenticate traffic between DataStax agents and the main OpsCenter daemon.
Enabling HTTPS
You can enable or disable Hypertext Transfer Protocol Secure (HTTPS) support in OpsCenter.
Configuring events and alerts
The OpsCenter Event Log page displays a continuously updated list of events and alerts.
Configuring data collection and expiration
OpsCenter collects system and column family metrics data for each node in your cluster.
Configuring OpsCenter definition file updates
Definition files are used by OpsCenter to enable support for different versions of DataStax Enterprise, DataStax Community, and Cassandra. They are updated independently of OpsCenter by downloading new definitions from a central server at regular intervals.
Advanced configuration
To configure advanced capabilities, you can manually modify the configuration files.
Backing up opscenterd's configuration files for failover
This task describes how to manually backup the configuration files of
opscenterd
in case of a failure of the primary
opscenterd
instance.
Using custom start/stop scripts for DataStax Enterprise and Cassandra
OpsCenter allows users to start and stop the DataStax Enterprise/Cassandra process on each node in a visual way. The agent will attempt to automatically determine the best way to do this, but cannot not do so in all cases. You can customize the startup or shutdown of a node using the
start-cassandra
and
stop-cassandra
scripts located in
/usr/share/datastax-agent/bin
(package installs) or
<install_location>/bin
(tarball installs).
Example scenarios
Examples of OpsCenter deployments.
Configuration
Configuring user access
Configuring SSL
Enabling HTTPS
Configuring events and alerts
Configuring data collection and expiration
Configuring OpsCenter definition file updates
Advanced configuration
Backing up opscenterd's configuration files for failover
Using custom start/stop scripts for DataStax Enterprise and Cassandra
Example scenarios
