> Probes and Agents > Probes > Data persistence on Windows probes

Data persistence on Windows probes

When adding a probe, you can configure the probe's data persistence settings. This enables the probe to cache data for a specified length of time if the connection to the MSP N-central server is down.

For information on adding a probe, see Adding a Windows probe.

If the data being cached begins to exceed the specified length of time or the available disk space, the data is discarded based on the drop policy. The drop policy determines if MSP N-central discards the oldest or newest data. If the drop policy is configured for the oldest data, then the oldest record is discarded as each new record is cached. If the drop policy configured for the newest data, then any new data is immediately discarded.

During the time that the connection between the probe and MSP N-central is down, the status of the monitored services appear as stale. Once the connection to the MSP N-central server is restored, the probe transfers the cached data to MSP N-central. MSP N-central compares the most recent information in the cached data to the original data before the connection went down to determine if the service status has changed. If there is a change, the new service status appear on the dashboards and MSP N-central triggers the appropriate notifications.

For example, if the status was green before the connection went down, but red in the last record of the cached data sent to the central server, when comparing the two, MSP N-central triggers a notification. The data, can still be retrieved through historical reports.

Cached Data using Newest Drop Policy

If the last record of the cached data sent to the MSP N-central is green, then a notification is not triggered.

Cached Data using Oldest Drop Policy


Data is not cached for any asset-discovery tasks.