DiagnosticSource Execution for Resources
Last updated - 08 December, 2025
LogicMonitor enables you to run user created and LogicMonitor supported out-of-the-box DiagnosticSource modules to fetch diagnostic data to help troubleshoot issues directly from a Resource. You can run multiple DiagnosticSources at the same time across one or more resources, but the same module cannot be run in parallel on a single resource.
Note: Manual execution of DiagnosticSource is currently not supported for Kubernetes clusters.
LogicMonitor supports the following execution status for a DiagnosticSource module:
| Execution Status | Indicates |
|---|---|
| Not started | The DiagnosticSource module is not yet run. |
| In Progress | The DiagnosticSource module is currently running. |
| Success | The DiagnosticSource module is run successfully and has collected relevant data. |
| Invalid Request | LogicMonitor server received an invalid JSON request. |
| Reject | LogicMonitor Collector could not handle the incoming request from the server. |
| Exception | The DiagnosticSource module failed to run due to an error in Collector. |
| Timeout | Timeout occurs when a script fails to execute due to reasons such as the resource is dead, Collector is down, and so on. |
After running the DiagnosticSource, you can view the results generated by the script. This helps identify root cause of the issue you created the DiagnosticSource for. You can view the history of DiagnosticSource module run on a resource. The history provides details of the issues and the diagnosis performed to identify the root cause. You can view the execution history of a resource for a specific time range.
Requirements for Executing DiagnosticSource
To run a DiagnosticSource module, you need the following:
- The Security settings configured by enabling the Allow Execution of Diagnostic Sources switch to execute DiagnosticSources
For more information, see Security Settings. - A LogicMonitor user with Diagnostic Source permissions for the resource group in the Resources permission set
For more information, see Resources Role Permissions. - EA Collector 38.400 or later installed
For more information, see Adding Collector. - DiagnosticSource modules in My Module Toolbox and applied to the resources
For more information, see Configuring DiagnosticSource. - Resources including cloud resources monitored by local Collectors
For more information, see Enabling Cloud Monitoring using Local Collector.
Executing a DiagnosticSource
- In LogicMonitor, navigate to Resource Tree.
- Locate the resource to which a DiagnosticSource module is applied.
- Select the Diagnostics tab.
- In the Actions column, select
Run for the DiagnosticSource that you want to execute.
Warning: When the system begins to execute the DiagnosticSource, you cannot pause or cancel the execution.
The system runs the DiagnosticSource module and updates the execution status as In Progress.

When the process is complete, you can view the latest output in the Overview tab.
Note: If the script output is large, it is truncated to a maximum size of 32 KB.
Viewing DiagnosticSource Execution Results
- In LogicMonitor, navigate to Resource Tree.
- Locate the resource to which a DiagnosticSource module is applied.
- Select the Diagnostics tab.
- Select a DiagnosticSource.
By default, the Overview tab displays the following details:- Name of the DiagnosticSource
- Recent execution status
- Date and time when the DiagnosticSource execution started and ended
- Username of the user who executed the DiagnosticSource
- Output details
- Option to view output in fullscreen mode, download, and copy the output

Viewing DiagnosticSource Execution History
- In LogicMonitor, navigate to Resource Tree.
- Locate the resource to which a DiagnosticSource module is applied.
- Select the Diagnostics tab.
- Select a DiagnosticSource.
By default, the Overview tab displays. - Select the History tab.

- (Optional) Select a time range.
- Select a record to view the execution history.
