This page addresses frequently asked questions and common troubleshooting topics for the ABV Python SDK. For bug reports, please open a ticket on bug report form. For general questions or support, visit our support page.Documentation Index
Fetch the complete documentation index at: https://docs.abv.dev/llms.txt
Use this file to discover all available pages before exploring further.
- Authentication Issues:
- Ensure
ABV_API_KEYandABV_HOST(if not using default host) are correctly set either as environment variables or in theABV()constructor. - Use
abv.auth_check()after initialization to verify credentials. Do not use this in production as this method waits for a response from the server.
- Ensure
- No Traces Appearing:
- Check if
tracing_enabledisTrue(default). - Verify
sample_rateis not0.0. - Ensure
abv.shutdown()is called or the program exits cleanly to allowatexithooks to flush data. Manually callabv.flush()to force data sending. - Enable debug logging (
debug=TrueorABV_DEBUG="True") to see SDK activity and potential errors during exporting.
- Check if
- Incorrect Nesting or Missing Spans:
- Ensure you are using context managers (
with abv.start_as_current_span(...)) for proper context propagation. - If manually creating spans (
abv.start_span()), ensure they are correctly ended with.end(). - In async code, ensure context is not lost across
awaitboundaries if not using ABV’s async-compatible methods.
- Ensure you are using context managers (
- Media Not Appearing:
- Ensure
ABVMediaobjects are correctly initialized and passed ininput,output, ormetadata. - Check debug logs for any media upload errors. Media uploads happen in background threads.
- Ensure
- Enable debug logging to gather more information.
- Check the ABV status page.
- Raise an issue to our support with details about your setup, SDK version, code snippets, and debug logs.