- About LogicMonitor
- Cloud Monitoring
- Dashboards and Widgets
- Getting Started
- LM Service Insight
- About LogicModules
- Creating & Managing DataSources
- Active Discovery
- Data Collection Methods
- Groovy Support
- PowerShell Support
- Setting Up JobMonitors
- Help & Troubleshooting
- AppliesTo Functions Directory
- SNMP sysOID Maps
- Rest API Developers Guide
- RPC API Developers Guide
- Servicenow CMDB Integration
- Terminology Syntax
LogicMonitor often adds, updates and improves LogicModules – both as the LogicMonitor product gains capabilities (for example, the addition of MongoDB monitoring) and as we incorporate feedback from customers into our best-practices alerts.
Importing new or updated LogicModules
We do not automatically push out new versions of LogicModules to customer’s accounts, because customers often modify and tune their LogicModules. There is also a risk of certain LogicModule updates removing historical data (see below information).
Thus, importing new LogicModules must be explicitly triggered. To do so, navigate to Settings | LogicModules and click on the desired LogicModule. From there, select Add | From LogicMonitor Repository. Accept (click save) the default credentials to access the repository. You should see a dialog like this:
It is generally safe to accept any New LogicModules into your account (you can sort by the Status column) – however, this may result in new monitoring, and thus possibly new alerts – for some systems.
For LogicModules with a status of Show Diff, clicking the Show Diff link will show the difference between the core LogicModule and the one in your account:
From the Show Diff page, you can then perform one of three actions:
- You can choose to manually update your LogicModule with the changes (i.e. in another browser window, manually update each part of the LogicModule that is different: adding in the descriptions, or new datapoints, etc)
- You can choose to import the core LogicModule into your account – but be aware that doing so can result in the loss of some data. For substantial changes, it is recommended that you clone your existing LogicModule prior to the import. This will create a copy of the current LogicModule that does not apply to any hosts, but can be used to refer to after the import, to compare changes pre- and post- import.
- You may also decide that while there are differences between the core LogicModule and yours, the differences are not significant. (such as a choice of a different graph legend.) In this case you can, from the Show Diff screen, click the Mark Differences as Audited button at the bottom. This will change the Status column to “Audited – show diff”. This Audited attribute will stay there until the core repository LogicModule is changed again.
When LogicModule updates may result in the loss of historical data…
Warning: there are cases where historical data can be lost when importing an updated LogicModule.
Cases where data will be lost include:
- where a datapoint is renamed or removed in the updated LogicModule. (If the datapoint has been renamed, you may manually edit your LogicModule to make it accord with the current name, without losing data.)
- where Active Discovery has changed such that instances are now discovered with different names
- Keep in mind that for some LogicModules – especially those that simply report status values (e.g. power supply status, etc) – there is little use in keeping the history, so importing an updated LogicModule is generally safe. In most other cases, the updates are the additions of datapoints, adjustments of thresholds, or changes to graphs – no data will be lost.
Please contact support if you wish to discuss which updates are significant to apply, and how.
When LogicModule updates may result in the loss of custom changes & thresholds…
Warning: updating a LogicModule will overwrite any custom changes that you may have made to the LogicModule template. This includes any added or removed datapoints, revised thresholds, changes to graphs, polling intervals, etc. However, custom alert thresholds that are set on the device or device group level are not removed.