Oracle jdbc JAR file update
LogicMonitor's collector utilizes an outdated version of the Oracle JDBC jar file. It's essential to upgrade to the most recent version available in the Maven repository to take advantage of new secure database connection types. However, users should note a significant change in behavior with the new jar: while the old version automatically closed abandoned Oracle database connections, the new version does not, potentially leading to an excessive number of open connections. This surge in open connections can overload and crash an Oracle server where connections aren’t limited by user. Therefore, clients must either ensure that customizations explicitly close database connections or adjust their server settings to impose limits on the number of concurrent open connections. All of the newest Logicmonitor datasources properly close connections but some of the older modules did not do this. Logicmonitor has created a module to test for this problem and alert if it occurs. Oracle_Database_MonitorUser will keep track of the number of connections in use by the monitoring user and alert if the number of connections is too high. This update is scheduled for collector 35.400. Make sure this module is installed before upgrading to collect 35.400 and monitor your database connections before rolling this out to general release.
Off Cycle Datasource Updates
I saw in another post that there was an off cycle update to a Meraki Datasource due to a found bug. Is there a place we can be notified of such off cycle updates? I am just thinking of the situation where if we utilized that, but didn’t realize there was a bug and we wouldn’t update for a long while.SSL_Certificates DS v1.7 discovery issues
I pulled this version of the DS into my sandbox and tested on a few devices. The discovery task fails catastrophically. Can anyone else confirm? At any rate, be careful when LM changes something so fundamental as the discovery script is such a radical way. I’m in favor of the change (pulling props from the certificate instead of generic labels), but sometimes bad updates get published.Module Update Differences Report
I mentioned on the webinar today that I’d post an example output from my diff script. I’m not going to attach it here, so I’ll link to it instead. It’s an HTML page and it’s an older version of the script output, but opening it in your browser (use incognito if you’re worried) will show the list of modules whether they’re UpdatedNotInUse, UpdatedInUse, or New. Clicking on the blocks under a module (red=there’s a difference, green=there’s no difference) will show the existing vs. new versions. To generate this report, all I need is a RO set of credentials with view access to modules (I think). I use this as my checklist of updates to address. I have the history and existing definition on there (Old JSON) because I like to know if my version is out of date because LM changed an LM setting or if they changed something I had customized. And the old JSON is on there in case I need to revert (which I haven’t had to yet).