-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Instrument the SimpleLogProcessor from sdk/log
#7548
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
Open
yumosx
wants to merge
16
commits into
open-telemetry:main
Choose a base branch
from
yumosx:inst-slp
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+278
−4
Open
Changes from 9 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
0481fcb
feat(sdk/log): add observability instrumentation to SimpleLogProcessor
yumosx 402892c
added TestSimpleLogProcessorObsevability.
yumosx 66c7301
add failingTestExporter
yumosx 0788d3f
use counter
yumosx 0541716
fix the test and added bench
yumosx 16b8496
Merge remote-tracking branch 'upstream/main' into inst-slp
yumosx 8d4cd7f
add changelog entry
yumosx ca0e076
fix the markdown lint
yumosx a8fae0c
fmt
yumosx 3b942bd
move the counter to observ
yumosx 2bec291
Merge branch 'main' into inst-slp
yumosx 9addd81
Merge remote-tracking branch 'upstream/main' into inst-slp
yumosx bd7e92f
Update CHANGELOG.md
yumosx 53019cb
Merge remote-tracking branch 'upstream/main' into inst-slp
yumosx 1c9ec32
revert.
yumosx b7e05a9
Merge branch 'main' into inst-slp
yumosx File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm thinking that when this part of the logic is triggered, this section should also be reported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@flc1125, I don't quite understand this part.
could you explain it in detail?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What I want to express is that we should also report this metric regarding this part of the situation.
However, what's a bit special here is that what is returned here is
nil, but I'm wondering, when reporting the metric, should we define a custom error to describe the fact that it wasn't successfully exported (something like:simple processor has no exporter configured).cc @MrAlias, if you have any good suggestions, please feel free to add them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@flc1125 about this issue, maybe we could address this in an separate PR, WDYT?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we at least need to support indicators reporting for this scenario; the point of disagreement lies in the issue of
errornil.Regarding the points of disagreement, I think it's fine to discuss them in another PR or issue.