Launching a debugging session
This curl
command kicks off a multiverse debugging session.
curl --fail -u 'user:password' \
-X POST https://<tenant>.antithesis.com/api/v1/launch/debugging \
-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 using 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 access your session ~5-10 minutes after you call the webhook. If your request is malformed (e.g. an invalid parameter) you’ll receive a non-200 response or a failure email almost immediately.
Once you have the access link, you can start debugging in the Antithesis Notebook This session will be available for six hours.
Using multiverse debugging means direct access to your system under test. For this reason you must set up SSO to use this tool.