Instance Level Thresholding

With the Instance Level thresholding feature, you can set specific thresholds for predefined config checks and severity levels for a ConfigSource instance.
A ConfigSource LogicModule can monitor multiple resources, and a resource can have single or multiple instances. In such cases, Thresholds set at the ConfigSource level are the same for all the instances.
Examples of multiple instances are Running, Start-up, Inventory, and so on. 

Setting Global Config Checks

1. Log in to LogicMonitor > Modules > select the required ConfigSource.
2. On the ConfigSource page, in the Config Checks section, select Add Check.
3. On the Add Checks window, enter the following details:
   
   • Name – Enter the name of the check.
     
   • Check Type – Select the required check type from the drop-down list.
     
     Note: Add the additional details depending on the selected Check Type. For more information, see Creating ConfigSources.
     For config instance thresholding, you can add four types of Config checks: Config cannot be retrieved, Any change, Missing Field,  and Value.
     In addition, The Groovy Script Check Type is not supported.
   • Then trigger this type of alert – Select the alert type. For example; warning, error, or critical.
     
   • Description – (Optional) Add the description for the check.
     
     
     
4. Select Save.

Viewing Config Checks

1. Log in to LogicMonitor > Resource Tree > select the required ConfigSource instance.
2. On the ConfigSource pane, select the Alert Tuning tab.
3. Select the Alert Tunning tab to view all the ConfigSource details.
   
   
   
4. (Optional) Select the required Config Check, Check Type, or Severity to view or edit the details.
   After you select any of the options mentioned above, the ConfigSource edit panel is displayed.
   
   
   
   After you have updated the information, in the top-right corner of the edit panel, select the Save icon.
   
   Note: If you want to reset the changes to global settings, select the Global icon.
5. (Optional) Select the Alert Routing tab to view where the alert is routed.
   
   Note: You can also send a test alert to see if the alert is getting routed as configured by selecting Send Test Alert.
   
   
6. Select the required ConfigSource name in the Set at column to view the global settings.
   In the Set at column, you can see the Configchecks that are set at the Global or Self (instance) level.
   
   
   
7. Select the Configs tab to view the details of the alert type, severity, alert summary, and so on.
   
   

9. (Optional) Select the Alerts tab to view if any alerts are generated.
   
10. Select the Reported At value for the required resource. For more information, see Managing Alerts from the Alerts Page.
    A panel is displayed with Overview, Logs, Alert Generated Version, and History details.
    
    
    
11. Select the Alert Overview section, to see at which level threshold is referred to trigger an alert that is the Global level threshold or the Instance level threshold.
    
    – Global Level: If the alert is generated at the global level, the message “Threshold Level: Global” is displayed in the Overview section.
    
    
    
    – Self/ Instance Level: If the alert is generated at the instance or self-level, the message “Threshold Level: Self” is displayed in the Overview section.
    
    

Changing Threshold at Instance Level

To change the instance level from Self to Global or vice-versa, complete the following steps:

1. Log in to your LogicMonitor portal.
   
2. Navigate to the Resources > select the required ConfigSource instance.
   
3. In the Alert Tuning Configs Slot section, complete the following steps:
   
   
   • From Global Threshold to Instance Level Threshold: Select the Config Rule tab, make the required changes, and update the Note field.
     
   • From Instance/Self to Global Level Threshold: Select the Config Rule tab, make the required changes, update the Note field, and select the Revert to Global icon.
     
4. Select Save.

You can see the instance has changed from the Global level to the Self-level.

Viewing Change History

You can view or track the changes made to the instance level Config checks.

1. Log in to your LogicMonitor > Resource Tree > select the required ConfigSource instance.
2. In the Alert Tuning Configs Slot section, select History.

In the History tab, you can view the following information related to the config checks:

• Name of the user who made the changes
• The time when the changes are made
• Changes in the severity level or config type
• Changed, updated or deleted the config values
• Instance level changed from Global to Self or vice-versa