Pranav/diff log level for otlp and stdout#335
Draft
pranavpadmasali wants to merge 3 commits into
Draft
Conversation
- Add common/telemetry package with OTLP metric/log export via gRPC or HTTP, configurable TLS, compression, histogram boundaries, and SIGHUP hot-reload. - Bridge zap logger to OTel log exporter so structured logs ship to OTLP backends alongside metrics without duplicating the log pipeline. - Expose Logger.Meter() so components obtain named OTel meters from the logger directly, removing need for a separate telemetry handle. - Wire telemetry init into beegfs-remote, beegfs-sync, and beegfs-watch entry points with graceful Shutdown on exit. - Replace expvar-based scheduler metrics with OTel instruments and add common/scheduler and rst/remote workermgr tests covering the new metric paths.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What does this PR do / why do we need it?
Required for all PRs.
Related Issue(s)
Required when applicable.
Where should the reviewer(s) start reviewing this?
Only required for larger PRs when this may not be immediately obvious.
Are there any specific topics we should discuss before merging?
Not required.
What are the next steps after this PR?
Not required.
Checklist before merging:
Required for all PRs.
When creating a PR these are items to keep in mind that cannot be checked by GitHub actions:
For more details refer to the Go coding standards and the pull request process.