I just posted ldms_core 3.4.7, which integrates some of the feedback and discoveries of the last few weeks... thanks for all the help, folks. Debugging help and feature suggestions from LANDesk admins around the world are making this utility into a very useful tool indeed.

Here's a few notes about where it might (or might not) go next:

• Scheduled Tasks
•   
   
  •  
   
  • Check scheduled tasks and policies for RRD stats -- jobs without start times, jobs in success-level buckets, duplicated jobs...   
        
   
  •  
   
  • Delete ghost devices from scheduled tasks (stuck in active because they reported status). If they were from a query they should be deleted from the list, but if they were from a static targeting they should be moved to pending. http://community.landesk.com/support/message/17222#17222   
        
   
  •  
• Import   ldms_delete_users, auto-reassign to single user or delete objects, give the user an option to decide what should be done. Alternatively, rewrite ldms_delete_users as a standalone tool...
• NMAP as an XDD client add-on instead of a core-side piece... this implies some command-channel use and data-passing which are non-trivial, but entirely possible. On the plus side, it will also produce a much higher level of accuracy in OS fingerprinting.
• Email
•   
   
  •  
   
  • Be smart about hysteresis... maybe it could not send another email within a day unless the new email it wants to send is more urgent than the last email that it had to send? Users going from daily runs to hourly runs are having challenges sorting the important emails from the repetitive info.
   
  •  
   
  • Maybe it's email worthy that unmanaged nodes isn't fresh...   
        
   
  •  
• Web pages and reports
•   
   
  •  
   
  • In RRD pages, give textual data supporting the graph. That'll probably push it over the edge to needing templated data instead of straight html.   
        
   
  •  
   
  • Support proxy servers (nice to have for update check, will need for geo-location)   
        
   
  •  
   
  • Give links to non-RFC1918 addresses on maps: GeoIP2Location   
        
   
  •  
   
  • Drill-down from topology map with per subnet listings of computers, including inventory and remote control links for them   
        
   
  •  
• Auto-import email from domain controller into ConsoleUser table. If UserName is like Directory and Email is blank, then import from AD. Requires AD credential input in UI.
  
• Count duplicate serial number records and show a count before the number... e.g. "34 machines with serial number SystemSerialNumb, 2 machines with LYAC12"
• More options, more smarts, more feedback, more efficiency...
  
• Find why McAfee silently stops it from working properly when it's run as a scheduled task (error 0x9 in Windows scheduled task, immediate "success" as a LANDesk scheduled task, works great when run interactively from the start menu).

Version 2.9.2 solves the memory consumption problem for large core servers in a very simple way... do the NMAP scanning before creating the big lookup table, not after. You should see the system tray icon pop up, a couple of items in the event viewer, then a whole lot of nothing until it's done with your unmanaged nodes table, then a rapid spike in RAM usage for about thirty seconds before it sends the mail (if necessary).

I also fixed a stupid Oracle brackets bug (thanks Dustin), and changed debugging behavior. I was enabling database trace at level 9 while in debug mode. Then someone crashed their wimpy database server, so I quit doing that. If you want database trace, do it with the database tools or use the Perl script and uncomment the if debug then trace lines. I also discovered the Perl::Critic module, which totally rocks and helped me clean up some subtle issues.

Should be nearly as good as bacon now. Get yours at http://www.droppedpackets.org/scripts/ldms_core/ldms_core_2-0.zip/download

I found a stupid bug in the service stopping routine when I applied the 5-08 rollup to my core, so this fixes that. I also added a "check for the latest version" routine that I'd been working on anyway.