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.

  • Introduction
  • How Antithesis Works
  • Getting started
  • Package your software
  • Make it go
  • Deploy to Antithesis
  • Launch a test run
  • User manual
  • Properties and Assertions
  • Properties in Antithesis
  • Assertions in Antithesis
  • Properties to Test For
  • Sometimes Assertions
  • Test Composer
  • Test Composer Basics
  • Test Composer Reference
  • Principles of Test Composition
  • Checking Test Templates Locally
  • Webhooks
  • Launching a test
  • Retrieving logs
  • Launching a debugging session
  • Webhook API
  • Reports
  • Triage report
  • Bug report
  • Multiverse debugging
  • Overview
  • Exploring the multiverse
  • Querying with event sets
  • The Environment and its utilities
  • Using the Antithesis Notebook
  • Cookbook
  • The Environment and Multiverse
  • The Antithesis Environment
  • Fault Injection
  • CPUID
  • Reference
  • Handling External Dependencies
  • SDK reference
  • Go
  • Tutorial
  • Instrumentor
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • Java
  • Tutorial
  • Instrumentation
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • C
  • C++
  • Tutorial
  • C/C++ Instrumentation
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • JavaScript
  • Python
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • Rust
  • Tutorial
  • Instrumentation
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • .NET
  • Languages not listed above
  • Assert (reference)
  • Lifecycle (reference)
  • Tooling integrations
  • CI integration
  • Discord and Slack integrations
  • Configuring Antithesis
  • Instrumentation
  • User management
  • Sizing your deployment
  • Best practices
  • Is Antithesis working?
  • Optimizing for Antithesis
  • Finding more bugs
  • FAQ
  • About Antithesis POCs
  • Release notes
  • Release notes