migrate-to-autotel

Migrating observability tools to autotel requires replacing your existing SDK initialization code with autotel's init function. The process provides detailed step-by-step guides for each tracing source to ensure a smooth cut-over while preserving data fidelity during deployment.

Yes, you can transition from Datadog APM, Sentry, New Relic, Honeycomb beelines, or OpenTracing to autotel. The migration supports multiple tracing sources by providing specific strategies and code changes tailored to each tool's setup process.

The best way to switch from raw OpenTelemetry SDK to autotel is by replacing your existing SDK initialization code with autotel's init function. This approach ensures continuous monitoring without dashboard gaps or data loss during the transition.

Yes, autotel supports migration from OpenTracing and OpenCensus observability setups. It guides developers through the necessary setup modifications and validation processes to ensure a safe and effective transition from these legacy tracing standards.

To validate your observability setup after migrating to autotel, follow the outlined validation processes provided for your specific tracing source. This ensures continuous monitoring is maintained and verifies that no trace data was lost during the cut-over.