Retrieving logs

The triage report includes logs for your system leading up to each of the identified test failures. However, due to resource limitations in the browser, especially verbose logging may result in these logs being truncated. The get_logs endpoint allows you to request the full, unfiltered logs if needed.

Calling the endpoint with curl looks like this:

curl --fail -u 'user:password' \
-X POST https://<tenant>.antithesis.com/api/v1/launch/get_logs \
-d '{"params": { 
        "antithesis.debugging.session_id":"d5d1c9cf0e64b5dd69b00e97b07fe3f4-18-1",  
        "antithesis.debugging.input_hash":"-9067336385060865277" , 
        "antithesis.debugging.vtime":"45.334635781589895", 
        "antithesis.report.recipients":"YOUR_EMAIL@DOMAIN.com" 
    }}'

You’ll need to provide the parameters antithesis.debugging.session_id, antithesis.debugging.input_hash, and antithesis.debugging.vtime, which are obtained from the copy moment button in the triage report. For more details on webhook authentication and parameters see our Webhook API reference.

You’ll receive an email with a link to the relevant logs within 5-10 minutes. If your request is malformed (e.g. an invalid parameter) you’ll receive a non-200 response or a failure email almost immediately.