Changing the data collection time of the Portal

Changing the starting time of data collection

To change the default time of data collection in the Portal:

1. Log in to the Appliance that hosts the Portal.

2. Optional: If the Portal has no configuration file yet, that is, if portal.conf does not exist in folder /var/nexthink/portal/conf, create it by copying the defaults from the sample configuration file: sudo -u nxportal cp /var/nexthink/portal/conf/portal.conf.sample \ /var/nexthink/portal/conf/portal.conf

3. Edit the configuration file of the Portal: sudo vi /var/nexthink/portal/conf/portal.conf.

4. Add the following lines to the configuration file of the Portal, or modify their values if they are already present. For example, to start the data collection at 2h20: # Time (hour) at which collection for the previous day takes place globalconfig.portal.collector.time-to-collect = 2 # Time (minutes) at which collection for the previous day takes place globalconfig.portal.collector.time-to-collect-minutes = 20

5. Save your changes and exit the vi editor: :wq

6. Restart the Portal: sudo systemctl restart nxportal

Note that the actual time for triggering the nightly computation depends on how you configure the time zone of the Portal and the Engines.

Changing the maximum number of days collected

Every night, the Portal usually collects data of metrics for the past day only. However, for those metrics with their last days empty of data (because they could not be computed or because their history was cleared), the Portal computes not only the past day, but the number of days configured (up to the maximum number of days available in each Engine).

To set a different number of days to go back and compute metrics with no history, add the following line to the configuration file of the Portal. For instance, to compute five days of history, type in:

globalconfig.portal.collector.nb-of-days = 5

By default, the Portal goes back 3 days in the past to compute metrics when the data for their last days are missing. Set the configuration variable to -1 for the historical computation to go back up to the maximum number of days available in each Engine. Remember that computing metrics for dates in the past has some limitations.

The operations described in this article should only be performed by a Nexthink Engineer or a Nexthink Certified Partner.

If you need help or assistance, please contact your Nexthink Certified Partner.

---

RELATED REFERENCES

• Computing dashboard data

• Time Zones and data collection