Launching a debugging session

This endpoint kicks off a multiverse debugging session for a target test run that’ll be available for six hours.

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.

The target test run is identified by antithesis.debugging.run_id. For backwards compatibility, antithesis.debugging.session_id is also accepted but prefer run_id for new integrations.

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

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",
}
}

You can request a debugging session using either antithesis.debugging.run_id or antithesis.debugging.session_id. Although they are not marked as required below, you must provide either one of them in your request.


antithesis.debugging.input_hash

string · required

Obtain the input_hash from the copy moment button in the triage report.


antithesis.debugging.run_id

string

Run ID of the test run you want to start debugging. Obtain it from the runs view by copying from the ⋮ menu of the run, or by copying it from the bottom of the triage report.

Although this parameter is not marked as required, you need to provide either the run ID or the session ID of the test run to debug in the request. Prefer run_id over session_id for new integrations.


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.

Although this parameter is not marked as required, you need to provide either the run ID or the session ID of the test run to debug in the request. Prefer run_id over session_id for new integrations.


antithesis.debugging.vtime

string · required

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"
  • Introduction
  • Welcome to Antithesis
  • How Antithesis works
  • Using Antithesis with AI
  • Get started
  • Setup guide
  • Overview
  • For Docker Compose users
  • For Kubernetes users
  • Test an example system
  • Overview
  • With Docker Compose
  • Overview
  • Build and run an etcd cluster
  • Add a test template
  • With Kubernetes
  • Overview
  • Build and run an etcd cluster
  • Add a test template
  • Product
  • Test templates
  • Overview
  • Creating test templates
  • Test commands
  • How to check a test template locally
  • How to port tests to Antithesis
  • Test launchers
  • The triage report
  • Overview
  • Findings
  • Environment
  • Utilization
  • Properties
  • Logs Explorer & multiverse map
  • Debugging
  • Overview
  • Causality analysis
  • Multiverse debugging
  • Simple Multiverse debugging
  • Advanced
  • Overview
  • The Antithesis multiverse
  • Querying with event sets
  • Environment utilities
  • Using the Antithesis Notebook
  • Cookbook
  • Tooling integrations
  • CI integration
  • Discord and Slack integrations
  • Issue tracker integration - BETA
  • Configuration
  • Access and authentication
  • The Antithesis environment
  • Best practices
  • Docker best practices
  • Kubernetes best practices
  • Optimizing for testing
  • Concepts
  • Properties and Assertions
  • Overview
  • Properties in Antithesis
  • Assertions in Antithesis
  • Sometimes Assertions
  • Properties to test for
  • Fault injection
  • Overview
  • Types of faults
  • Pausing faults
  • Fault events in logs and reports
  • Reference
  • Webhooks
  • Overview
  • Launching a test
  • Launching a debugging session
  • webhook reference
  • Antithesis API
  • Handling external dependencies
  • SDK reference
  • Overview
  • Define test properties
  • Generate randomness
  • Manage test lifecycle
  • Assertion catalog
  • Coverage instrumentation
  • Go
  • Go SDK
  • Instrumentor
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • Java
  • Java SDK
  • Using the SDK
  • Building your software
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • C SDK
  • C++
  • C++ SDK
  • C/C++ Instrumentation
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • JavaScript
  • Python
  • Python SDK
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • Rust
  • Rust SDK
  • Instrumentation
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • .NET
  • .NET SDK
  • Instrumentation
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • Languages not listed above
  • Fallback SDK
  • Assert (reference)
  • Lifecycle (reference)
  • Assertion Schema
  • FAQ
  • Product FAQs
  • About Antithesis POCs
  • Release notes
  • Release notes
  • General reliability resources
  • Reliability glossary
  • Techniques for better software testing
  • Autonomous testing
  • Deterministic simulation testing
  • Property-based testing
  • White paper — How much does an outage cost?
  • Catalog of reliability properties for key-value datastores
  • Catalog of reliability properties for blockchains
  • Test ACID compliance with a ring test