-
Notifications
You must be signed in to change notification settings - Fork 2.7k
feat: add more spans to opentelemetry plugin #12686
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Nic <[email protected]>
Signed-off-by: Nic <[email protected]>
Signed-off-by: Nic <[email protected]>
| end | ||
|
|
||
| if code then | ||
| if code >= 400 then |
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.
Without this, we would need to add a tracer.finish_current_span call in every core.response.exit() code, which is very troublesome.
| } | ||
|
|
||
|
|
||
| function _M.new(name, kind) |
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.
TODO: reuse span table if there has any proformance issue.
Description
Run jaeger in local by https://www.jaegertracing.io/docs/2.11/getting-started/#all-in-one
Which issue(s) this PR fixes:
Fixes #
Checklist