chore(otel): raise exception if exporter unavailable #234
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zastrowm
approved these changes
Jun 16, 2025
pgrayy
pushed a commit
to pgrayy/sdk-python
that referenced
this pull request
Jun 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This is a followup to #232. After speaking with @zastrowm we agreed that it is better to explicitly raise an exception if a customer relies on Strand's internally configured OTEL HTTP exporter. The goal is to avoid a situation where a customer has deployed a Strands agent to production and after #232 their telemetry is no longer being exported. The overall blast radius of this change is minimal as outlined in #232.
Related Issues
Documentation PR
Planned for a separate PR. Tracking issue: https://github.com/strands-agents/private-sdk-python-staging/issues/76
Type of Change
Testing
hatch fmt --linterhatch fmt --formatterhatch test --allChecklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.