Analytics

Analytics can be enabled on Horizon to speed search and dashboards on certificates, events and discovery events.

It will create an embedded analytics database on each of the Horizon and store a copy of those objects.

This will increase RAM and CPU consumption on the horizon server itself, but will reduce load on the database.

The analytics database is only used for research; all other operations are done directly to the mongo database

You should consider enabling the analytics if you have slow interfaces due to a large number of certificates or events

Configuring the analytics

To enable analytics, extra configuration has to be added to Horizon following this guide.

The following configuration key is used to set up the analytics database file:

horizon.analytics.url = "jdbc:duckdb:/opt/horizon/var/analytics.db"

The following configuration keys are used to enable the analytics on certificate, event and/or discovery event.

horizon.event.analytics.enabled = true
horizon.discovery.event.analytics.enabled = true
horizon.certificate.analytics.enabled = true

The following configuration keys are additional parameters for advanced configuration:

horizon.analytics.pool-size = 10
horizon.analytics.memory-limit = "1GB"

Environnement variables are available to configure the analytics see the docker analytics parameters.