When Will My Module Toolbox Work Properly?
So we recently received a banner in one of our portals stating that in a future release the LogicModules section will no longer be available. This concerns us greatly as I noticed something after I just had a new portal spun up. I logged in, went to the Modules section in the new UI and told it to show me all of our outdated items. Nothing shows up. I then went into the Exchange, told it to show me all of the Installed and Update Available. Nothing shows. I also checked for anything Official that isn’t installed, and nothing shows up.So I naturally go the legacy route, load up DataSources, and tell it to look at the repository. Lo and behold, I have 85 DataSources. Some are new, some are updated. We were told at one point that the Modules/Toolbox/Exchange area look at a different repository, so we gave the benefit of the doubt and checked one of the new modules and an updated module, and both were 3 months old and not showing up in the new UI. Stu brought up some concerns as well inUpdates to modules showing in repo but not modules toolbox | Community (logicmonitor.com), but I didn’t want to necro post with a slightly different issue.
Parity? What is that?
So, this is happening at some point. Today, given the release of several updates to modules, I decided to abandon my really good workflow and the coolest tool LM never built in favor of the modules toolbox. Sigh. There’s no option that I can find to “show associated devices”, which in the old UI showed a list of devices with their associated instances. You could even filter to only show those devices that had instances. There was a CSV download option. It was great because you could tell the difference between a module applying to 500 devices that have instances and applying to 500 devices that didn’t have any instances. It’s the difference between impact and no impact. Later, I needed to clone at propertysource. The existing one was fine, just needed to add some stuff for a different purpose. Guess what there is no button for in the module toolbox? Cloning a module. On the plus side, there is now a “use status” column for display and filtering. That helps a ton. This isn’t a parity issue, but there’s a new “deprecated” indicator for those modules that have been deprecated. You know what you can’t find without going somewhere else? Which module replaces it. I really, really hope the old ship doesn’t get scuttled before the new ship can even float.
My Module Toolbox Pro-Tips
As a Customer Success Manager here at LM, I wanted to share a few key features found in our new Module Toolbox that have made keeping LogicModules up to date easier than ever! Search functionality Upon opening your Module Toolbox (found among your tabs under the Reports tab), you will notice there is a search bar in the top left. This will allowyou to search for any specific modules instead of spending time combing through looking for the one you need! Multiple filters You can now filtermodules you’re searching for by type (datasource, eventsource, configsource, etc.) as well as by customized, skipped updates, author, group, status and report! Bulk updating You now have the ability to update your modules in bulk(-given that you don’t have any customizationson the modules you have selected). This is going to savetime when it comes to keeping your modules up to date, rather than having to update them one by one.If you have customized modules, simply select the filter for “customized” and select “no”. From there you can select all and update. ba-da-boom! Customization preservations This is one that so many of our customers have been asking for. When updating a customized module, again, select the filter for “customized” and select “yes”. From there you will click the update button (depicted as an up arrow inside a circle) on the module you’d like to update. Review any changes made to the module in the diff viewer, click final review and then you will see a “Preservations” option on the right hand side which allows you to preserve customizations made to that particular module. You can currently preserve settings for Active Discovery filters, AppliesTo, Collection Interval, Discovery Interval, Display Name, and Group. No more updating the module to only have to go back in and rewrite all your customizations! Happy updating! :)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).