Investigate user session logging failures #1199
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📥 Pull Request
📘 Description
This PR addresses a critical issue where AgentOps sessions would appear to initialize (displaying a session URL) but no data would reach the backend due to silent authentication or export failures. The changes introduce robust diagnostic tools and significantly enhance error visibility to empower users in debugging connectivity problems.
Key improvements include:
agentops.diagnose_session()
andagentops.print_session_status()
to provide detailed, user-friendly reports on SDK health, authentication status, and export statistics.agentops.helpers.debug_session
) and an example script (examples/debug_session_connectivity.py
) for comprehensive end-to-end connectivity testing.🧪 Testing
The changes were validated by creating and running the new
examples/debug_session_connectivity.py
script. This script utilizes theagentops.helpers.debug_session.test_session_connectivity
function to simulate various scenarios (e.g., no API key, invalid API key, successful authentication) and verify that the improved error reporting, color-coded URLs, and diagnostic outputs behave as expected.