Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > User Device Tracker (UDT) > Things to consider when adjusting the default UDT polling settings

Things to consider when adjusting the default UDT polling settings

Table of contents

Updated March 15, 2017


This article details why UDT polling is set to 30 minutes by default and what are the things to consider before adjusting the settings.


All UDT versions



As an example, polling was set at 5 minute intervals and not all the alerts for the new MAC addresses did not trigger.

Some reasons as to why it did not work.

Job Time: First off, the time it takes for the jobs themselves to run can greatly vary. Some devices are able to provide their data through SNMP very quickly, so you tend to see no issue. Some however are spending more CPU processing threads on actual data transfers across ports\routes, resulting in the SNMP processes to be delegated to a lower thread. That means that it takes longer for the SNMP results to be returned in the job, hence causing the jobs to take much longer
Data import: UDT is one of the most SQL intensive applications that we have in terms of I\O. So even if a job finishes on time, the results themselves may not show up in the database immediately. Sometimes that data is delayed a few minutes as it finishes other result updates.

View update for the alert: This pertains to the second one above as well. After all the results are in, the view then has to populate with those results. This can be delayed as well as a lower process priority.




Last modified