Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA 4.2.2 Administrator Guide > NTA settings > Historical updates

Historical updates

Changing IP groups, applications, or NetFlow sources are referred to as update operations.

If you change IP Address Groups, Applications or NetFlow source settings, the changes will also be applied on historical data. The most recent data will be updated first, and then older data stored during the retention period.

As a consequence, two or more users are able to make changes affecting the same applications or IP Address Groups at the same time.

Running updates in NTA resources

If an update is running, all relevant resources will inform you about it. The data in the resource might be inconsistent, because historical data are being updated.

The warning message in the resource includes completion percentage. The shown percentage depends on the time settings in the resource.

For example, say a resource showing the last three hours of data informs you that an update is affecting it, and that 50% is complete. If you change the time frame to the last hour, the percentage of already updated data will rise. However, if you expand the time frame to last month, the completion percentage is much lower.

You can set how often resources should refresh when an update operation is running. Navigate to NTA Settings > Charting and Graphing Settings, select Automatically Refresh Resources Affected by Running Updates, and adjust in minutes.

About change request conflicts

SolarWinds NTA displays a message if you make a change that conflicts with a change by another administrator. Conflicting change requests might cause some of your changes to fail. Possible causes of conflict include:

  • Two administrators changing the same application or IP Address Group at the same time.
  • An administrator modifying an application while another administrator is changing an IP Address Group relevant for the application.

Resolve a change request conflict

  1. Review the conflict message, and submit your changes.
  2. Verify that your changes have been submitted successfully.
  3. If some changes are not submitted, repeat the changes, and submit them again.
 
Last modified
08:57, 13 Apr 2017

Tags

Classifications

Public