These docs are for v6.6. Click to read the latest docs for v6.7.

Timeseries RRD

Description

Opsview Timeseries RRD (opsview-timeseries-rrd) provides a Timeseries storage framework. It consists of dedicated RRD Updaters and RRD Queries processes to maximize the throughput.

Note: This cannot be installed at the same time as opsview-timeseries-influxdb.

RRD Updaters

Opsview Timeseries RRD Updaters launch master management process that binds to the configured ports and launches that many worker processes each responsible for handling the requests for given port. That provides the guarantee that the data sent from Opsview Timeseries Enqueuer for given host is handled by single process only, thus removes the risk of processing the data out of order. The metadata (including the uoms) is stored in the SQlite3 database.

RRD Queries

Opsview Timeseries RRD Queries provide a way of querying the gathered performance metrics and listing them.

Dependencies

Opsview Timeseries RRD can be installed on any supported platform. To reduce network traffic it is recommended to install it on the same host as the Opsview Timeseries Enqueuer component.

Installation

Refer to Advanced Automated Installation.

Configuration

If opsview-timeseries-rrd was installed on other then Opsview Timeseries or Timeseries Enqueuer host, you need to update the /opt/opsview/timeseriesrrd/etc/timeseriesrrd.yaml file to listen other then loopback interface.

timeseriesrrd:
    server:
        # username and password for HTTP Basic authorization
        user: opsview
        password: opsview
        # Updater that receives the metrics data
        updates:
            # IP to listen on, use 0.0.0.0 to listen on all interfaces - needs to be reachable by Opsview Timeseries Enqueuer
            host: 127.0.0.1
            # ports used by each worker
            workers:
                - port: 1640
                  port: 1641
                  port: 1642
                  port: 1643
            logging:
                loggers:
                    opsview:
                        # syslog compatible log level, at INFO level HTTP requests are logged
                        level: NOTICE
        queries:
            # IP to listen on, use 0.0.0.0 to listen on all interfaces - needs to be reachable by Opsview Timeseries
            host: 127.0.0.1
            # port to listen on
            port: 1660
            # number of pre-forked subprocesses handling the incoming requests
            workers: 4
            logging:
                loggers:
                    opsview:
                        # syslog compatible log level, at INFO level HTTP requests are logged
                        level: NOTICE
    # data directory where RRD files are stored
    data_dir: /opt/opsview/timeseriesrrd/var/data
    # default settings for created value.rrd files
    rrd:
        # Heartbeat. In seconds, twice the size of servicecheck intervals
        # Increased to 1 hour 10 minutes so graphs for checks set at 1 hour intervals
        # do not have gaps if the run interval is 60 minutes and 1 seconds or more
        heartbeat: 4200
        # base interval in seconds
        step: 300
        # round robin archives
        archives:
            - RRA:AVERAGE:0.5:1:600
            - RRA:AVERAGE:0.5:6:700
            - RRA:AVERAGE:0.5:24:775
            - RRA:AVERAGE:0.5:288:797

All configurable options are listed in the /opt/opsview/timeseriesrrd/etc/timeseriesrrd.defaults.yaml and /opt/opsview/timeseriesrrd/etc/timeseriesrrd.yaml.example.

Service Administration

As root, start, stop and restart the service using:

/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-timeseriesrrdupdates
/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-timeseriesrrdqueries