Context, Instance, & Logs

During a test run, Antithesis searches for violations of all the properties you have defined, and summarizes the results in a triage report. The inputs to a bug report are from a previously conducted test run, and one particular property that you want investigated in detail.

Since Antithesis may have found many ways to violate the property in question during a single test run, Antithesis will choose one or more instances of the property being violated, showing the same bug appearing in different situations and contexts.

Bug context

This section restates the inputs that were used to generate this report: it shows which specific property failure on which specific test run provided the data for the report.

Bug instance details

This lists several different instances of the property violation we found. For each instance, it shows a log excerpt at the moment that the bug was detected, and some information necessary to deterministically reproduce the issue. Clicking on an instance in this section will change what the entire rest of the report refers to, for example, changing the logs displayed, here and in the logs section below.

Logs

The Logs Section shows the full set of logs generated over the course of running the selected bug instance. This includes application logs, system journal messages, and other information you may need to understand the bug in question. You can customize what’s included in your bug reports.

You can also search and filter for particular log messages, using either substrings or regular expressions. You can also select which services or software components should have their logs included, using the button on the top left.

Most importantly, you can click at a point on the likelihood graph to go to the corresponding point in the logs.