Retrieving logs
This endpoint allows you to request full, unfiltered 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.
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.
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 must have SSO set up to use this endpoint.
Authentication
Antithesis webhooks use basic auth credentials for authentication.
USER:PASSWORD
The basic auth machine credentials for your tenant.
<TENANT>
Your tenant’s name.
Parameters
These parameters are passed as JSON according to the following template:
{
"params": {
"parameter1_name": "parameter1_value",
"parameter2_name": "parameter2_value",
}
}
The required parameters are marked with a *
.
antithesis.debugging.input_hash *
string
Obtain the input_hash
from the copy moment button in the triage report.
antithesis.debugging.session_id *
string
Session ID of the test run you want to start debugging. Obtain it from the copy moment button in the triage report.
antithesis.debugging.vtime *
string
The vtime at which you want to start debugging. Obtain it from the copy moment button in the triage report.
antithesis.report.recipients
string
A ;
-delimited list of recipients who’ll receive emailed links to the triage report produced by this test run.
If this parameter is not specified, emails will be sent to the default users set up for the endpoint.
Examples:
"antithesis.report.recipients": "u1@site.com; u2@site.com"