Network Management
Things to consider when adjusting the default UDT polling settings
This article discusses the reason why UDT is set to 30 mins by default and what to consider before adjusting this settings.
First published date
Last published date
Overview
Product section
Resolution
For example, when polling is set to a 5-minute interval, not all the alerts for the new MAC addresses are triggered.
There might be several reasons for this issue:
Job Time
First off, the time it takes for the jobs 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, 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.