Sending OpsCenter metrics to a Graphite server 

Configure sending metrics from OpsCenter to a Graphite server. This is an OpsCenter Labs feature in development.

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

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

Configure forwarding metrics from OpsCenter to a Graphite server. This is an OpsCenter Labs feature (that is, under ongoing development but available for use). OpsCenter pushes metrics at a hard-coded interval of 60 seconds.

Graphite stores time-series data and renders static graphs of the data. If your organization uses Graphite in its reporting infrastructure, you can easily integrate the data collecting power of OpsCenter with the open source Graphite monitoring tool.

Procedure

  1. Open cluster_name.conf for editing. Substitute cluster_name with the name of your cluster. Setting agent options through the cluster configuration file sets the corresponding property in address.yaml on every node.
    If necessitated by your environment, open address.yaml for editing. Do so for every node that requires a specific configuration override.
  2. Add the following configuration options:
    [labs] graphite_host
    Setting graphite_host enables the forwarding of metrics to a graphite server at the given address. Leaving the graphite_host blank disables forwarding metrics to the graphite server.
    [labs] graphite_port
    Port for graphite's plaintext protocol.
    [labs] graphite_prefix
    A prefix to insert metrics under.
    [labs]
    graphite_host = 127.0.0.1
    graphite_port = 2003
    graphite_prefix = opscenter
  3. Save the configuration file or files.
  4. Restart the OpsCenter daemon.
  5. Optional: If you made changes to address.yaml, restart the DataStax agents.