Michael_Dieter
NeophyteJoined 9 years ago
User Profile
Neophyte
User Widgets
Contributions
Re: Non-Admin Collector install
Running the collector install, you get prompted for user credentials (an account that is local admin) with privilege to install software. One should use this account to run the collector installer but supply a different (non-admin) user account at the prompt during installation? This answer may be self-evident to some, but I find the instructions not clear and seem to rely on implicit assumption by the reader instead of explicit intent by the technical content team.Non-Admin Collector install
After trying to navigate through all the ramifications of Collector Least Privilege, I considered the option of simply getting new VM servers and installing new collectors with a "least privilege" user account. I'm fortunate enough that we have sufficient compute and storage resources that my request for new VMs can be delivered, and then I can remove the old collectors from service and our server virtualization team can delete them (returning those compute and storage resources to the available pool; net impact is 0). This seems like it will be less overall headache and effort than running the LM-supplied scripts. So I'm just going to throw this screen shot out there, for public consumption, of the install ---being done with the intent of moving to "Least Privilege"---recommending Domain Admin/Local Admin. Sure, maybe this is just an artifact in the installer presentation?Documentation page Disclaimer
I've noticed several of these recently while digging for information on multiple topics. None of them offer any further context about why, when the info on this page stops being valid (calendar date, collector version?), or where to go for update/replacement info. Anybody have any insight? 🤔APC UPS Logicmodule datapoint addition
I'm requesting to please add a pair of datapoints to the Official LM-authored Logicmodule: APC UPS Status (locator NKG6DE) Input voltage .1.3.6.1.4.1.318.1.1.1.3.2.1.0 Input frequency .1.3.6.1.4.1.318.1.1.1.3.2.4.0 There are some locations on our campus where we'd like to track these values. We believe there are periodic variations in them that may be responsible for otherwise unexplainable behavior in certain wiring closet HW. There appears to be UPS capability to mitigate this but we'd like the data these datapoints collect to inform the necessary UPS configurations, and we'd also like to have the data to present to our Facilities Electrician team to help them diagnose and correct house power delivery where appropriate. We are working on this DIY, but we would much prefer to see it released officially so that we can minimize customizations.Re: Create a LogicModule status alert
FWIW: we haven't updated vmware monitoring nor meraki monitoring in almost a year. Still waiting onanswersandanswersfrom LM for the VMware stuff. Well that's super cool. Thanks for the heads up; I had not previously seen that thread. In this case I can extricate myself from the rabbit hole (of which I was unaware that I was in) without too much damage done and observe the progress on the that thread before choosing to proceed with more replacements.Re: Create a LogicModule status alert
Stuartyou 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.Create a LogicModule status alert
Release notes have been including notice about deprecated logicmodules and indicated replacements for a while and this is great. I would like to request that consideration be given to what I think would be even better. A few ideas: the current way that replacement modules are presented in the Release Notes (side by side columns limited by screen real estate and page layout) can make it tedious to conclusively determine which module is the replacement since often the text of names wraps to additional lines. So finding some way change to change this presentation that shows an unequivocal 1:1 relationship between a deprecated module and its replacement would be awesome. If 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? 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? 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?) Maybe an OOB dashboard with a widget that dynamically populates a table when a Logicmodule in My Toolbox status changes to "deprecated" and includes its replacement?Re: Ping Failing from collector to device and back?
This behavior seems like it may be related to, or overlap with, an issue I first observed in January 2020 (I think) and was never able to resolve. Randomly, subsets of our Juniper switches (and only switches, no other devices) would trip alerts indicating 100% ping loss. It would usually auto-resolve after 60-90 minutes and never left evidence behind--that I could find--why the condition started or cleared up. During the time the alerts were in effect,I had other non-collector sources of pings to the same switches that were not disrupted and I could ping back to the collectors involved from the switch command line. SSH, SNMP, other communication between collectors and switches showed no problem. Of note, none of the traffic between collectors and switches traversed a firewall. The real kicker to me was that I had never seen this behavior until I upgraded collectors to 29.003. If I rolled collectors back to 28.x, the issue did not occur. As soon as I pushed forward again to 29.x it started happening again. I opened a case with support and I spent a lot of tedious time trying to figure out where traffic was getting dropped to no avail; after several monthsI was not able to convince them to move from their “its something in your environment” stance. As much as I wanted an answer I simply could not afford to devote the time needed to sustain an investigation. Ultimately I applied system.category “NoPing” to switches and moved on.Re: Ideas for tracking LM website docs changes?
👆 +10 I think this isn’t something that isn’t unique to LM, but it would be hugely helpful if they were able to figure out a way to add a calendar dimension to documentation content, a trail of milestones or a mechanism that let us essentially “flip back to a previous page”
