feat(telemetry): Expose OpenTelemetry exporter init arguments in API #365
+35
−10
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
jer96
approved these changes
Jul 7, 2025
poshinchen
approved these changes
Jul 7, 2025
There was a problem hiding this comment.
Could you update the docs following the README: https://github.com/strands-agents/docs
I've opened a PR in the documentation project: strands-agents/docs#162 |
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 PR enhances the StrandsTelemetry API by allowing users to pass arbitrary keyword arguments (**kwargs) directly to the constructors of OpenTelemetry's
ConsoleSpanExporterandOTLPSpanExportervia thesetup_console_exporterandsetup_otlp_exportermethods. This exposes the full configuration surface of these exporters to downstream users, enabling more flexible and advanced telemetry setups. Docstrings have been updated to clarify this behavior. No breaking changes are introduced, and all setup methods remain chainable.Related Issues
#363
Documentation PR
strands-agents/docs#162
Type of Change
New feature
Testing
How have you tested the change? Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli
hatch run prepareChecklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.