Neophyte
MastermindIf you navigate to MyToolbox and select a module, the bottom half of the screen opens with details about this module. There is a tag present that says "In Use". Maybe another tag could be created that says "Deprecated" and clicking on it takes you to the replacement module? In the reverse direction, if you navigate to the Exchange and select a module, maybe there could be a "Replacement For" tag, that if clicked upon takes you to the module/s that it replaces?
The "Support" column shows either "Community", "Deprecated", "Official", or "Blank". Haven't seen any documentation around what they all mean, but the deprecated modules usually have that notated there. I love the idea of something pointing to the module that replaces it.
What about if there was some way to create an OOB filter & Saved/Favorite view in My Toolbox that presents a list of deprecated modules, each with a clear mechanism that matches it to its replacement?
I do this today. I have one called "Deprecated - In Use":
And i have one called "Deprecated - Not In Use":
Find some way to generate an alert (probably even with its own icon/color to give it maximum distinction in the Alerts Tab/table) when a module's status changes to 'deprecated' and have the alert message text includes exact replacement module details (Origin ID?)
I used to do this with the old modules API endpoints that were undocumented. It would be nice if there were documented/supported endpoints for pulling this. I used to get alerts within the hour when pushes were made to the repo. Now, I have to have a scheduled task to go in and manually look at all my saved filters to see what might need my attention.
NeophyteStuart you are an on-point power user in a way that I cannot be 😀
All of your suggestions are available now to ID those that are deprecated but what would really make things better is the second part of my ideas -->an (unambiguous/unequivocal/stupid simple easy button) indicator to ensure the 1:1 relationship between the deprecated version and the version that replaces it, to lead me to selecting the right replacement. I can filter My Toolbox for Deprecated, but I can't remember seeing any one of them cite the replacement. I recently had a situation where I disabled alerting for a deprecated VMware datasource and installed what I thought was the correct replacement. Turns out I was not paying close enough attention in my replacement selection off of the table in the Release Notes: I did not install the correct replacement so for a time we had no alerting. Thankfully we noticed (just barely) before the lack of alerts caused a real problem.
MastermindStuart you are an on-point power user in a way that I cannot be 😀
haha, thanks. Just means that we are both experiencing the same issues. It was honestly embarrassingly simple to build that stuff. The only problem was that it used undocumented/unsupported endpoints that eventually stopped working as the toolbox started taking precedence. LM should have built it out of the box.
All of your suggestions are available now to ID those that are deprecated but what would really make things better is the second part of my ideas -->an (unambiguous/unequivocal/stupid simple easy button) indicator to ensure the 1:1 relationship between the deprecated version and the version that replaces it, to lead me to selecting the right replacement. I can filter My Toolbox for Deprecated, but I can't remember seeing any one of them cite the replacement. I recently had a situation where I disabled alerting for a deprecated VMware datasource and installed what I thought was the correct replacement. Turns out I was not paying close enough attention in my replacement selection off of the table in the Release Notes: I did not install the correct replacement so for a time we had no alerting. Thankfully we noticed (just barely) before the lack of alerts caused a real problem.
Yes, the idea about linking the deprecated version to the new version would be awesome. FWIW: we haven't updated vmware monitoring nor meraki monitoring in almost a year. Still waiting on answers and answers from LM for the VMware stuff.
