Professor
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
Concerns us greatly as well since one of our value-adds is that our LM is always up to date with the most recent security patches and bug fixes available. I used to have modules imported within 1 business day of them being released.
Stu brought up some concerns as well in Updates 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.
I have no issue with you necro posting. It’s the same issue: “it doesn’t have the same results as the existing method”
Hi
@Joe Williams , did you have the proper filters enabled in Module Toolbox to return all the desired results?
One of my big complaints. What are the right filters to do? Is there documentation on how to do that? if it’s the same for everybody, why not make a dashboard for us? Or at least build the filters into the favorites so every user doesn’t have to try to mimic a screenshot. I have 4 saved filters on the toolbox (updated in use, updated not in use, deprecated not in use, deprecated in use) and 2 in the exchange (new, not ready for the light of day (can anyone spell vmware?)). The filter isn’t in the URL either (like it is in LM Logs) so i can’t share a link to a set of modules with another admin. I have the same complaint about alerts: give me a query language like LM Logs.
Why are they different places again? Put the “installed/not installed” filter in “my modules” and list everything. Why can i go to the exchange and see “installed & up to date/installed & update available”? Wouldn’t i just see that in “my modules”? If everything is listed in the exchange, why would i use “my modules” at all?
Previously, i had a datasource that would do the API call every 4 hours to check for updates. That way I’d get notified when there were updates that needed my attention. Are the API endpoints available? No. My module update workflow used to be event driven. Now it can’t be. So i either spend time each week checking for updates that may not be there to stay up to date or I check less frequently and run the risk of being out of date for longer.
It’s difficult to trust LM anymore. They say, “we’ll make sure we have feature parity before we remove the old capability”, but its debut has been announced without parity in sight. Stop going after new features (dexda?) and fix the broken stuff!