Skip to content

Add a ConfigProvider callback for runtime instrumentation option changes#8076

Open
jackshirazi wants to merge 3 commits intoopen-telemetry:mainfrom
jackshirazi:config-provider-callback
Open

Add a ConfigProvider callback for runtime instrumentation option changes#8076
jackshirazi wants to merge 3 commits intoopen-telemetry:mainfrom
jackshirazi:config-provider-callback

Conversation

@jackshirazi
Copy link
Contributor

First step in adding support for runtime changes to options, focusing only on API additions.

The assumption is that if an instrumentation is able to handle changes at runtime, it will register a callback against the ConfigProvider instance that the otel SDK is using.

Further steps (to be discussed):

  • Add spec change for runtime config updates and listener semantics
  • Expose getConfigProvider() in the SDK API
  • Provide a "change mechanism" for example, mutable provider or equivalent update source
  • Add implementations

@codecov
Copy link

codecov bot commented Feb 12, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.19%. Comparing base (0a1a2ce) to head (164ea55).

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #8076      +/-   ##
============================================
- Coverage     90.20%   90.19%   -0.01%     
  Complexity     7594     7594              
============================================
  Files           841      841              
  Lines         22915    22916       +1     
  Branches       2290     2290              
============================================
  Hits          20670    20670              
  Misses         1529     1529              
- Partials        716      717       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jackshirazi jackshirazi marked this pull request as ready for review February 12, 2026 15:43
@jackshirazi jackshirazi requested a review from a team as a code owner February 12, 2026 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant