Forrester Total Economic Impact™ study finds Edwin AI delivered a 313% ROI for composite organization.

Read more

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 StatusIndicates
Not startedThe DiagnosticSource module is not yet run. 
In ProgressThe DiagnosticSource module is currently running. 
SuccessThe DiagnosticSource module is run successfully and has collected relevant data. 
Invalid RequestLogicMonitor server received an invalid JSON request. 
RejectLogicMonitor Collector could not handle the incoming request from the server.
ExceptionThe DiagnosticSource module failed to run due to an error in Collector.
TimeoutTimeout occurs when a script fails to run due to reasons such as the resource is dead, Collector is down, and so on.

When the DiagnosticSource execution is complete, you can view the result generated by the script. You can view the execution history of a resource for a specific time range. The history of DiagnosticSources provides details of the issues and the diagnosis performed to identify the root cause. 

You can view the output in JSON or plain text format. You can select the format that suits your needs. Details of the supported formats are as follows: 

  • JSON format—In the JSON format, the rendered output is contained in a “data” field. Most LogicMonitor supported DiagnosticSources provide output in JSON format to avoid issues with special characters, multiple languages, and to allow potential for future metadata for specifying rendering (html, markdown, and so on). 
    The following displays an example output in JSON format:
{
  "format": "md",
  "data": "|%CPU|COMMAND|\n|----|-------|\n|4.0 |systemd|\n|1.0 |sshd   |"
}
  • Plain text format—If the output is not a valid JSON in the “data” field, the output falls back to the plain text format.

Requirements for Running DiagnosticSource

To run a DiagnosticSource module, you need the following:

  • The Security settings configured by enabling the Allow Execution of Diagnostic Sources switch to run DiagnosticSources
    For more information, see Security Settings.
  • A LogicMonitor user with Diagnostics: Execute 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.

Running DiagnosticSource

  1. In LogicMonitor, navigate to Resource Tree.
  2. Locate the resource to which a DiagnosticSource module is applied.
  3. Select the Diagnostics tab.
  4. In the Actions column, select Run DiagnosticSource icon Run for the DiagnosticSource that you want to run.

Warning: When the system begins to run the DiagnosticSource, you cannot pause or cancel the execution.

The system runs the DiagnosticSource module and updates the execution status as In Progress.

DiagnosticSource tab on Resources page

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 Run Result

  1. In LogicMonitor, navigate to Resource Tree.
  2. Locate the resource to which a DiagnosticSource module is applied.
  3. Select the Diagnostics tab.
  4. 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 run started and ended
    • Username of the user who triggered the DiagnosticSource 
    • Output details
    • Option to view output in fullscreen mode, download, and copy the output
      DiagnosticSource execution result in Overview tab
  5. Select the History tab.
    DiagnosticSource Execution History of a Resource
  6. (Optional) Select a time range.
  7.  Select a record to view the run history.
    DiagnosticSource Execution Details in History tab

14-day access to the full LogicMonitor platform