Meant to say the "History" on the Search feature only provides stats from the previous day.
Can you raise a support ticket with regards to the missing information in the Port Details List resource on the Node Details page please. We'd need to get the diagnostics from you to look into this further. Let support know when you raise the ticket that you've spoken to the UDT dev team on thwack.
With regards to the history on the search page; how long has UDT been installed for on your system and are you using the default polling intervals (30 minutes)?
When you say only showing history stats from the previous day; are you looking at the 'LastSeen' date in the search results grid? What does the 'FirstSeen' date for this MAC (endpoint) say?
Also, you may want to check the filter options on the grid toolbar and if the connection type filter is showing 'Direct Connections', try change it to 'All Connection Types' to see if more historical records are returned.
When you open a support ticket, could you:
--Reference this thread to Support.
--Post back here with a case number.
--Post any solutions you get from Support.
Referenced this Thread with Support this Morning,
Case #245988 - "UDT Device unable to see all the information on node summery page"
Another anomoly ( It seems related) I am seeing now is on the Device Watch List list, on the main page its pulling the wrong switch in (yellow), yet when I drill down i get the correct switch and port.
Jason, the issue with the watchlist is a known bug. The watchlist shows you the devices connected but does not differentiate between direct and indirect connections. We plan to change this is the future (show the connection icon and give preference to direct connections).
Here is the latest information on the issue were having:
Update for Case #245988 - "UDT Device unable to see all the information on node summery page"
we just had feedback from development and it seems your Switch - Alder - 3750Router has both L2 and L3 capabilities.
There seems to be a bug with our store procedure if this is the case and development is currently working on a buddy drop in order to get this resolved.
We will update you as soon as we have received the buddy drop from development.
We apologize for any inconvenience.