Community Announcement: Sunset of LogicModules in Settings in Uiv3
Attention LogicMonitor Users,
In the upcoming release v207, we want to inform you about an important change regarding LogicModule management. Starting in release v207, LogicModules will no longer be accessible from the Settings page in UIv3. Instead, the Modules page (Toolbox and Exchange) will be the new platform for LogicModule management going forward.
What does this mean for you?
Changes to LogicModule Access: All LogicModule management, including adding, editing, and updating LogicModules, will now be performed exclusively through the Modules page (Toolbox and Exchange).
Accessing LogicModules: Please navigate to the Modules section from the LogicMonitor navigation sidebar to manage your LogicModules efficiently.
What’s Going Away?
The following functionalities under "Settings → LogicModules" in UIv3 will be deprecated:
- Add LogicModules (from LMX, Repo, or File)
- All Editors for LogicModule Types
- The LogicModule tree with Groups
- Update/Import from Core
NOTE: All the mentioned functionality exists in UIv4, except for "Import from Core" (although imports between customer portals are still possible with appropriate credentials, especially in child/parent/MSP setups). While the Group tree is not visually represented as a tree in UIv4, Groups are still accessible within the Modules UIv4 interface.
Customer Impact:
We understand that this change may require a slight adjustment to your workflow. Please refer to our detailed Modules Overview Documentation for guidance on utilizing the new Modules page effectively.
Additional Helpful Documentation:
Thank you for your attention to this important update. We are committed to continuously improving our platform and ensuring a seamless experience for our users.
pgordon
·2 years agoI would love to know what else is coming. I am still finding the process of keeping my customizations overly cumbersome. The settings to preserve certain parts of the module while accepting other parts of the update just aren't working for me. I've literally had to copy the JSON of the scripts in the comparison view, run them through something outside LM to get rid of the JSON formatting and escape characters, and go back to the edit screen to paste the updates to the scripts that I want. The current workflow still wants to get rid of any datapoints I've added and reset all the other toggles back to default (collection intervals for example).
If on the comparison screen I could scroll through and click an accept button for each section of changes I want, and by default keep the things that already exist, that would be so much better. Obviously I don't need to be able to accept each and every chunk of new whitespace in a script, I mean more so like to approve the whole new script instead of keeping the whole old script or not approving the removal of the datapoints I added etc.
LM User
·2 years agoYep, i have to do the same thing. Luckily we have a sandbox portal so i bring the updates into there and put the two windows side by side so i can copy/paste from one to the other. We particularly have problems when we have discovery settings like auto-deletion that cannot be preserved.
pgordon
·2 years agoThat's a good thought, I keep forgetting about the sandbox. Though, I'm sure you'd agree, it should just be easier to do without all that extra faff
LM User
·2 years agoYes, it should totally be easier. It was easier before when I used the undocumented api endpoint to pull down the data, used python to parse through and decode everything, then generate an HTML page that showed the current on the left, new on the right, with the diff actually showing the differences. They turned off access before I had a chance to do the next thing i wanted: put left/right toggles for each block between the left and right sides allowing me to pick which one i wanted to keep and output the final json (pretty much what your suggestion was). Hopefully they'll enable preservation for all fields and start showing the actual forms on the left and right instead of dumping raw json into a diff view.
Michael Rodrigues
·2 years agoAdding preservation options is a bit trickier than it might look.
We tried to go all out with SLM but it was too ambitious and didn't work properly (letting people preserve and/or edit pretty much everything).
We are looking to add preservation for Datapoints, possibly next quarter. I'd like to do scripts as well, but that will probably need to wait for the full "form based diff" experience, which would be next year at the earliest.
We're also looking to finally expose tag-editing to users, as well as a CSV export option for search results in Toolbox and Exchange.
LM User
·2 years agoI don't need preservation of scripts, i'd never trust it to get merged properly. I always do those manually as long as I'm the one that made the local version. If LM made the local version, it shouldn't show up as customized and those don't get as much scrutiny. But deleteInstances, discoveryERIInterval, postProcessorParameter on datapoints, doesAlertClearAfterACK for CSs, and offset under discoveryERIInterval are the biggest fields we need to preserve.
We also need an indicator if there are changes below the fold so we can know whether or not it's worth scrolling down for 15 feet just to make sure there are no other surprise diffs.
We also need the order not to register as a diff when the change in order was caused by a preservation. (I can show you this one if you want).