The driver used for storing and retrieving timeseries data.
Note: It's possible to use InfluxDB v.2 with a compatible v.1 bucket, however the Retention and the Buckets have to be managed by the InfluxDB GUI.
Minimum InfluxDB version supported: 1.5.1

The URL pointing to a running InfluxDB instance.

The database to use for timeseries storage. Existing data will not be migrated. In case an InfluxDB v.2 with a compatible v.1 bucket, put the bucket name.

Enable InfluxDB authentication.

The username to authenticate with the InfluxDB database.

The password to authenticate with the InfluxDB database.

The interval between consecutive timeseries data points for local hosts
NOTES:

• Lowering the resolution can create gaps in the existing data. It is advisable to delete the database .

Maximum duration in seconds for the InfluxDB queries. Queries exeeding this duration will be aborted.

Retention (days) for InfluxDB timeseries and top talkers. Default: 30 days.
Note: If InfluxDB is currently used, to change the retention policy correctly, ntopng restart is needed.
Note: If InfluxDB v.2 with a compatible v.1 bucket is used, the retention policy does not work.

Toggle the creation of bytes and packets timeseries.

Toggle the creation of Layer-7 application timeseries. Creating a timeseries per application requires more disk space and extra I/O and, in general, it is not needed.

Toggle between displaying a single total traffic timeseries (RX + TX) and separate timeseries for RX and TX. When the 'Total' option is selected (default), a combined timeseries is generated. Otherwise, separate timeseries are created for each direction (RX and TX).

Enable full host timeseries creation (full), limit it to bytes and score (light), or turn it off.

Toggle the creation of timeseries for one-way traffic. One-way traffic is often generated by remote hosts performing probing, so it is advisable to keep this disabled.

Toggle the creation of Layer-7 application timeseries. Creating a timeseries per application requires more disk space and extra I/O and, in general, it is not needed.

Toggle the creation of bytes and packets timeseries.

Toggle the creation of Layer-7 application timeseries. Creating a timeseries per application requires more disk space and extra I/O and, in general, it is not needed.

Toggle the creation of timeseries for monitoring the system, e.g. Redis timeseries, CPU/Memory timeseries...

Toggle the creation of bytes and applications timeseries for VLANs.

Toggle the creation of bytes and application timeseries for autonomous systems.

Toggle the creation of bytes timeseries for countries.

Toggle the creation of internals timeseries, e.g., hash tables entries, periodic activities duration and number of timeseries points written, scripts duration and number of calls.