Skip to content
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

otellogr: Implement LevelSeverity, Enabled #6206

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

scorpionknifes
Copy link
Member

This PR implements a few methods for otellogr package

  • Configurable LevelSeverity
  • Enabled

Please add skip changelog thx 🙏

Part of #5192

@scorpionknifes scorpionknifes requested review from pellared and a team as code owners October 5, 2024 12:50
Copy link

codecov bot commented Oct 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.1%. Comparing base (aaa6d68) to head (2830a0a).
Report is 10 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@          Coverage Diff          @@
##            main   #6206   +/-   ##
=====================================
  Coverage   67.0%   67.1%           
=====================================
  Files        194     194           
  Lines      12658   12671   +13     
=====================================
+ Hits        8492    8503   +11     
- Misses      3888    3889    +1     
- Partials     278     279    +1     
Files with missing lines Coverage Δ
bridges/otellogr/logsink.go 98.5% <100.0%> (+0.3%) ⬆️

... and 1 file with indirect coverage changes

@scorpionknifes scorpionknifes changed the title otellogr: Implement LevelSeverity otellogr: Implement LevelSeverity, Enabled Oct 5, 2024
@dmathieu dmathieu added the Skip Changelog Allow PR to succeed without requiring an addition to the CHANGELOG label Oct 7, 2024
)
otellogr.WithLoggerProvider(provider),
// Optionally, set the log level severity mapping.
otellogr.WithLevelSeverity(func(i int) log.Severity {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder what the use case is for this. When would folks want to change the severity mapping?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Skip Changelog Allow PR to succeed without requiring an addition to the CHANGELOG
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants