RemediationSource Configuration

Last updated - 29 May, 2026

You can create a RemediationSource that resolves issues such as high CPU usage, memory leakage, network connectivity issues, and so on. Configuring a RemediationSource consists of associating resources and resource groups to which the RemediationSource is applied. It also involves specifying a Groovy or PowerShell script to remediate issues and gather relevant data. Before saving RemediationSource details, you can test the script on a few resources to verify if the script returns the desired result. In case of an error, you can revise the script. This measure ensures that your RemediationSource performs as designed while resolving actual issues.

You can also import the following LogicMonitor-supported out-of-the-box Windows and Linux RemediationSource packages:

• Restart Linux Device—Runs the reboot command on a Linux system.
• Kill Linux Process—Terminates a process on a Linux system.
• Launch Linux Process—Launches a process on a Linux system using nohup.
• Restart Windows Device—Restarts a Windows device using PowerShell remoting.
• Suspend Windows Server Cluster Node—Drains and suspends a node in a Windows Failover Cluster.
• Resume Windows Server Cluster Node—Resumes a suspended node in a Windows Failover Cluster and brings it back online.
• Launch Windows Process—Launches a process or starts a Windows service.
• Kill Windows Process—Terminates a process or service on a Windows system.
• Microsoft Windows Disk Cleanup—Performs disk cleanup operations on Windows systems by removing temporary files, cleaning Windows updates cache, emptying Recycle Bin, and clearing system temporary folders to free up disk space.

For more information, see Importing a Module.

Requirements for Configuring RemediationSource

To configure RemediationSource modules, you need the following:

• A LogicMonitor user with resource permissions for “Remediation Source” settings for the resource group. For more information, see Resources Role Permissions.
• The “Manage” permission for all installed modules in My Module Toolbox. For more information, see Modules Role Permissions.
• To apply the RemediationSource to resources, including cloud resources, a Local Collector must monitor the resources.
  For more information, see Enable Monitoring via Local Collector.
• EA Collector 39.500 or later installed on your machine. For more information, see Adding Collector. 
• To test the remediation script, toggle the Enable Test Script switch on the Security settings page. For more information, see Security Settings.

Configuring RemediationSource

1. In LogicMonitor, navigate to Settings > LogicModules.
   The My Module Toolbox page displays.
2. Select Add.
   The Add modal displays.
   Alternatively, to add a RemediationSource, you can import a RemediationSource or clone an existing RemediationSource. For more information, see Modules Management.
3. Select RemediationSource.
   
   The Add RemediationSource page displays.
   
4. On the Info tab, do the following:
   1. In the Name field, enter a unique name for the RemediationSource.
      For example, you can specify the platform or application and, if necessary, a specific component of the platform.
   2. (Optional) In the Description field, enter enough details to ensure that the RemediationSource’s purpose can be determined.
   3. (Optional) In the Tags field, add tags to filter the module.
   4. (Optional) In the Group field, specify the group to which the RemediationSource is added.
   5. (Optional) In the Technical Notes field, enter any notes or technical information.
5. Select the Access Groups tab and configure access groups as needed. 
   For more information, see Access Groups for Modules.
6. Select the AppliesTo tab, and do the following:
   1. Enter the applies to criteria.
      The Applies to field accepts AppliesTo scripting as input to determine which resources can be associated with the RemediationSource.
   2. Select Test AppliesTo.
      This test returns a count of matching resources, and displays them in the AppliesTo Results panel.
7. Select the Script Preview tab, and do the following:
   1. Select an embedded PowerShell or Groovy script from the Collection Type dropdown menu.
   2. Based on the selected collection type, enter a Groovy or PowerShell remediation script to fix the issue.
      Note: Although the script you have entered is for testing, if the test completes successfully, you cannot undo script testing and the system automatically remediates the issue using the script. Verify all parameters before testing.
   3. Select  Test Script.
      The Test Collection Script window displays.
   4. In the Search Resources field, enter a value for a resource.
      LogicMonitor attempts to match values as you type.
   5. Select Run Test.
      The result of the script displays in the stdOutput.
      If the test script fails, details of the exception or error display in the stdError.
   6. Close the Test Collection Script window.
8. Select Save.

The RemediationSource is created and listed on the My Module Toolbox page.