Configure Horizon Core to Use Newts

Create a configuration file with the time series database settings

sudo vi etc/opennms.properties.d/timeseries.properties

Configure Newts as the time series strategy

# Configure storage strategy
org.opennms.rrd.storeByForeignSource=true(1)
org.opennms.timeseries.strategy=newts(2)

# Configure Newts time series storage connection
org.opennms.newts.config.hostname=cassandra-ip1,cassandra-ip2(3)
org.opennms.newts.config.keyspace=newts(4)
org.opennms.newts.config.port=9042(5)

# One year in seconds
org.opennms.newts.config.ttl=31540000(6)

# Seven days in seconds
org.opennms.newts.config.resource_shard=604800(7)

1	Associate time series data using the foreign source and ID instead of the database-generated node ID.
2	Set time series strategy to use `newts`. If you are enabling the dual write plugin on an existing installation and want to keep historical metrics, do not set the `org.opennms.timeseries.strategy` to `newts` until you have written enough data to expire any collected data prior to enabling the dual write feature.
3	Host or IP addresses of the Cassandra cluster nodes. Can be a comma-separated list.
4	Name of the keyspace which is initialized and used.
5	Port to connect to Cassandra.
6	Retention rate for the time series data.
7	Shard metrics every 7 days.

Initialize the Newts schema in Cassandra

bin/newts init

Connect to Cassandra with the CQL shell

cd ${CASSANDRA_HOME}/bin
./cqlsh

Verify if the keyspace was properly initialized

use newts;
describe table terms;
describe table samples;

Apply changes and verify your configuration

systemctl restart opennms

With this information set, upon restart, Horizon will begin persisting metrics using the Newts engine.

Go to the Node detail page from a SNMP-managed device and verify that you see response time graphs for ICMP and node-level performance data. Only metrics stored in Newts are displayed in graphs. If you have data in RRD or JRB files, they will not be displayed unless they are migrated to Newts.