-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: remove exception logging during evaluation #347
Conversation
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #347 +/- ##
==========================================
- Coverage 97.41% 97.41% -0.01%
==========================================
Files 26 26
Lines 1240 1239 -1
==========================================
- Hits 1208 1207 -1
Misses 32 32
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Is this affecting only the Python SDK or is it something that should be specified more generally? |
Logging isn't covered in the spec. We could consider general guidance but I would be reluctant to go any deeper than that. |
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
After approving, I'm actually considering if we should specify something here. I'm wondering if this is the wrong solution to the problem. I think we should be logging errors if a flag is not found, and that this change will make debugging harder. I think this is a situation where we'd want log-spam. |
This PR
Impacts
open-telemetry/opentelemetry-demo#1628
Notes
The OTel demo was seeing overly verbose log messages when they disabled a flag. That's because a
FLAG_NOT_FOUND
error was raised by the provider, and the SDK was logging all exceptions. I've updated the SDK to no longer log OpenFeatureErrors since providers commonly raise these, which can lead to log spam. It's worth noting that this information can still be accessed via a hook or evaluation details.