- play_arrow Troubleshooting a Problem
- play_arrow Common Problems
- Common Problems
- Troubleshooting DSMs
- Disk Storage Not Accessible Error
- Resolving Log Source Error After Protocol Update
- Verifying Disk Usage Levels
- Event FAQ
- Event Processing Performance
- Incomplete Report Results
- Resolving Limited Disk Space for Backup Partitions
- License System Notifications
- Resolving Login Errors with Active Directory Accounts
- Verifying That JSA Receives Syslog Events
- Fixing the Certificate Security Browser Warning
- App Host Migration Error
- Offenses are Slow to Load
- play_arrow Increased DNS Requests
- play_arrow JSA System Notifications
- JSA System Notifications
- Disk Usage System Notifications
- Asset Notifications for JSA Appliances
- Automatic Update Notifications for JSA Appliances
- Custom Rules Notifications for JSA Appliances
- Disk Notifications for JSA Appliances
- Event and Flow Notifications for JSA Appliances
- Failure Notifications for JSA Appliances
- Failure Notifications for QRadar Apps
- High Availability Notifications for JSA Appliances
- License Notifications for JSA Appliances
- Limit Notifications for JSA Appliances
- Log and Log Source Notifications for JSA Appliances
- Memory and Backup Notifications for JSA Appliances
- Offense Notifications for JSA Appliances
- Repair Notifications for JSA Appliances
- Vulnerability Scan Notifications for JSA Appliances
Running Health Checks
DrQ is an extensible health check framework for JSA. Run DrQ health checks before major events, such as upgrades, to determine whether there are any issues that need to be addressed first. You can also run DrQ routinely to monitor the health of your system. You can run all health checks at once, an individual check, or a group of checks.
DrQ is independent of each host and can be run only by the root user. When you run DrQ, it only has access to the files on the current host. It does not have the ability to communicate to any other host in the deployment. Each health check is designed to only run on the appropriate host.
To run health checks, type the following command.
drq
This command runs all available checks in /opt/ibm/si/diagnostiq with the checkup mode, and with the summary output mode.
The following table shows the general parameters for DrQ.
Parameters | Description |
|---|---|
-h | Shows the help information for DrQ. |
-l | Lists all tests and shows which are valid and which are not applicable to the system. |
The following table shows the filtering parameters for DrQ.
Parameters | Description |
|---|---|
-d <directory> | Run all checks in a directory. You can include this flag more than once, to specify multiple directories.
|
-f <filename> | Run a check by filename. You can include this flag more than once, to specify multiple checks.
|
-m | Run all checks in a mode. The default mode is checkup. |
-r | Recursively run all checks in a directory. You can include this flag more than once, to specify multiple directories.
|
-t <tag> | Run a group of checks by tag. You can include this flag more than once, to specify multiple tags.
|
The following table shows the output parameters for DrQ. These parameters are mutually exclusive.
Parameters | Description |
|---|---|
-j | Outputs json output of the check results. You can pipe the content to the jq tool to parse and format the json output.
|
-q | Runs in quiet mode. Outputs one of the following exit codes:
|
-s | Runs in summary mode. Outputs the number of successes and failures. This is the default output mode for DrQ. |
-v | Runs in verbose mode. Outputs success and failure messages for each check. |
