Automated Diagnostics

Linux OS & Applications

When responding to incidents related to Linux servers, there are many sorts of diagnostics that can be run. Unlike some cloud diagnostics, connecting to Linux servers will involve using node executors to connect. Node executors will be utilized by Runners with Runbook Automation or directly by servers with Process Automation (on-premise).
Node executors are configured as part of node definitions at the project level or per-node and then used as needed at job run-time by the Runner or server.

Often, Linux diagnostics are jobs composed of one or more command or script steps that gather data from the node about resources or services on that node.

Examples:

The following examples are included in our Automated Diagnostics Project, which can be downloaded here.

Check the health of a Linux service such as a web server or database

Parse server logs for common error messages

Syslog Queries For Common Errors

Collecting resource diagnostics from the server

Node Executors for Linux:

Process Automation and Runbook Automation offer multiple methods of communicating with Linux servers through the multiple Node Executors, such as these:

• SSH
• OpenSSH
• Ansible inventory
• SSM on AWS
• ECS container nodes
• OpenSSH using Bastion Hosts