Health checks are categorized as one of four severities: Low, Medium, High, and Test Failure.

Table 1.
Severity Description
Low These issues are unlikely to cause any functional failures but indicate that something is not as it should be (such as mismatched kernel and agent versions that are otherwise communicating and protocol-compatible).
Medium These issues will cause some use cases to fail but not affect others. For example, a failure might not affect execute operations but could interfere with write:block or device control rules.
High These are serious issues that indicate the agent software is not performing correctly and visibility, detection and protection capabilities will likely experience failures. These must be investigated and resolved before considering a deployment operational.
Test Failure These issues indicate that a specific health check test could not be executed. There may be a configuration problem (such as a missing installation package), an interoperability conflict (such as other security software interfering with the test), or an incorrect assumption in the test itself (such as the existence of certain files that might not be present on some embedded configurations). For test failures, the best diagnostics are to capture a debug level 6 (high or verbose) agent trace that includes the health check (For example: dascli debuglevel 6, dascli healthcheck, and dascli capture logs.zip).