2021-11-17 US Office Hours

[1:25] I recently discovered that a couple of our Collectors in a couple different ABCGs are provisioned with more memory than the others, so I bumped those with 16+ GB up to X-Large while the others are still Large. Is this a Really Bad Thing? I couldn't find anywhere in the docs that talks about good-or-bad for mixing Collector sizes in a Group, only that the versions need to be the same. Thoughts?
Oddly, the one I made X-Large has the least Instances!! It's been running for more than a month that way.
Does the load-balancing not happen based on CPU and/or memory load?
D'oh! Got it now.
I need more coffee apparently. Thanks!!!  ?

A: It's not necessarily a bad thing, but if the larger collectors go down you'll want to ensure the smaller ones have enough resources to collect the remaining resources that might have failed onto them. 



 

[20:10] Apologies if this was already covered, but how do I import a MIB file? I have my watchdogs monitored but none of the SNMP attributes show up.

A: There is currently no way to import a MIB file, but you can build an SNMP DataSource in Settings > DataSource and inputting the OIDs manually.




 

[33:04] We have a customer (we're a sort of MSP) where they want to have custom Thresholds and/or Alerting on/off for individual Instances of NetApp Volumes. Since Instances in this DS come from Active Discovery, I believe the only way to have per-Instance settings is to have an external script do that via API. Is that correct?

A: This is possible in the Alert Tuning tab if you select the instance in the Resource Tree.





[] What is the best practice for keeping these DataSources Updated? Does everyone simply update all of them on a scheduled basis?  Never update?
Our CSM got us a limited-use "sandbox" portal, where we import all new modules as soon as they are released, then after evaluation we bring them in to the prod portal. It's manual, but there are some API endpoints that might work. We do it manually because it's so quick to do with practice.

A: PropertySources, TopologySources, and AppliesTo Functions can be updated without much risk if you haven't customized them. With DataSources, you can obviously lose historical data, so you should be careful with these. However, if you're updating an unmodified DataSource provided by LogicMonitor, the updates are always backwards compatible unless otherwise specified in the release notes. These you can safely update. If you've made customizations to Collection, AD, or AppliesTo, you may lose data on update, and probably want to clone the module to a new name first. We're working on functionality in the LM Exchange that will allow you to preserve these customizations upon update.