Skip to main content

1. Initialize the SDK

Create an init file or add the SDK initialization to your application entry point. The SDK must be initialized before your application starts handling requests.
Ensure that TuskDrift is initialized before any other telemetry providers (e.g., OpenTelemetry, Sentry, etc.). If not, your existing telemetry may not work properly.

Initialization Parameters

OptionTypeDefaultDescription
api_keystrRequired if using Tusk CloudYour Tusk Drift API key.
envstros.environ.get(“ENV”, “development”)The environment name.
log_level”silent” | “error” | “warn” | “info” | “debug""info”The logging level.
sampling_ratefloat1.0Override the base sampling rate (0.0 - 1.0) for recording. Takes precedence over TUSK_RECORDING_SAMPLING_RATE and config file base-rate settings.
See also: Environment Variables guide for detailed information about environment variables.

Framework-Specific Setup

import os
from flask import Flask
from drift import TuskDrift

# Initialize SDK BEFORE creating Flask app
sdk = TuskDrift.initialize(
    api_key=os.environ.get("TUSK_API_KEY"),
    env=os.environ.get("FLASK_ENV", "development"),
    log_level="debug"
)

app = Flask(__name__)

@app.route("/")
def hello():
    return "Hello, World!"

if __name__ == "__main__":
    # Mark app as ready before starting server
    sdk.mark_app_as_ready()
    app.run(host="0.0.0.0", port=8000)

2. Configure sampling

Tusk Drift supports both fixed sampling and adaptive sampling. In fixed mode, the SDK records at a constant rate. In adaptive mode, the SDK starts from a configured base rate and can temporarily reduce recording if local exporter or runtime pressure increases. The base sampling rate uses the following precedence (highest to lowest):
  1. Init Parameter (sampling_rate)
  2. Environment Variable (TUSK_RECORDING_SAMPLING_RATE, with TUSK_SAMPLING_RATE kept as a legacy alias)
  3. Configuration File (recording.sampling.base_rate, or legacy recording.sampling_rate)
If not specified, the default base sampling rate is 1.0 (100%). The sampling mode defaults to fixed.
Set the sampling rate directly in your initialization code:
sdk = TuskDrift.initialize(
    api_key=os.environ.get("TUSK_API_KEY"),
    sampling_rate=0.1,  # 10% of requests
)

Recording Configuration Options

OptionTypeDefaultDescription
sampling.modestr”fixed”Selects constant sampling or adaptive load shedding.
sampling.base_ratefloat1.0The base sampling rate (0.0 - 1.0). In fixed mode this is the effective rate. In adaptive mode the SDK may temporarily reduce below this base rate.
sampling.min_ratefloat0.001 in adaptive modeThe minimum steady-state sampling rate for adaptive mode. In critical conditions the SDK can still temporarily pause recording.
sampling.log_transitionsboolTrueControls whether the SDK emits adaptive-sampling transition logs. Can also be overridden by TUSK_RECORDING_SAMPLING_LOG_TRANSITIONS.
sampling_ratefloatNoneLegacy alias for recording.sampling.base_rate. Still supported for backward compatibility.
export_spansboolfalseWhether to export spans to Tusk backend or local files (.tusk/traces). If false, spans are only exported to local files.
enable_env_var_recordingboolfalseWhether to enable environment variable recording and replaying. Recommended if your application’s business logic depends on environment variables.

3. Mark the app as ready

Once your application has completed initialization (database connections, middleware setup, etc.), mark it as ready:
sdk = TuskDrift.initialize(
    api_key=os.environ.get("TUSK_API_KEY"),
)

# Your application setup...

# Mark app as ready for recording/replay
sdk.mark_app_as_ready()
print("Server started and ready for Tusk Drift")
The mark_app_as_ready() call signals to the SDK that your application is fully initialized and ready to handle requests. This ensures that traces are only recorded for requests that occur after your application is properly set up. To record your first set of API tests with Tusk Drift, view this guide.