Use this procedure when the tracing library prevents startup, reports initialization errors, or produces no spans after deployment.

Checks

1. Confirm that the library version supports the application runtime and framework version.
2. Validate required configuration values and environment-variable names.
3. Check dependency loading and package resolution errors.
4. Verify that initialization occurs once and before application requests are handled.
5. Confirm that resource identity and exporter configuration are complete.
6. Reproduce with the smallest manually instrumented operation.
7. Compare startup logs before and after the tracing change.

Restore the last working version when tracing prevents the application from starting. Keep tracing initialization failures isolated from business logic where the library supports that behavior, but do not silently ignore repeated export or configuration errors.