Reviewing VERA results

Understand the report structure, metadata fields, and standardized status tags generated by VERA.

About this task

Every evaluated diagnostic check automatically displays an entry on the console standard output (stdout). If the --outdir parameter is specified at runtime, the application simultaneously generates and displays these entries to a report file named vera_report_<timestamp>.txt. This file serves as a log to verify system health, troubleshoot issues, or forward to the support team.

The status of each processed check is expressed through four standardized system output tags:
Status tag Description
[ OK ] The check passed validation successfully.
[FAIL] The check processed successfully but failed to pass the specific validation constraints defined in the JSON file. Remediation is required.
[ ERR ] A runtime process error occurred that prevented the check from completing (e.g. a command not found or a host permission denied error).
[ INFO ] Included only if the parameter capture_output is set to true. No validation logic is applied, and the output is stored for telemetry or informational purposes.
Each log entry written to the console or the text report file consists of five structured metadata components:
Report Field Component Captured Content and Behavior
Value Found The text output intercepted by VERA from the host system shell or internal routine.
Check Status The status tag assigned to the result.
Expected The target value literal, regular expression string, or numeric range required for the check to achieve a passing state.
Messages Custom success or failure log text strings declared within the JSON configuration file for that specific check block.
Operational Suggestions Actionable remediation steps and troubleshooting notes configured in the JSON file. It is displayed when a check returns a [FAIL] or [ERR] status.

Analyzing the output instantly isolates environment anomalies to ensure the target environment satisfies all configuration requirements prior to subsequent deployment phases. This verification streamlines local remediation or, if an issue requires deeper investigation, fast-tracks expert resolution by attaching the generated vera_report_<timestamp>.txt file directly to the technical support ticket.