-
Notifications
You must be signed in to change notification settings - Fork 821
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
feat: add express plugin #666 #685
Conversation
Codecov Report
@@ Coverage Diff @@
## master #685 +/- ##
==========================================
+ Coverage 91.11% 94.57% +3.46%
==========================================
Files 232 217 -15
Lines 10444 9981 -463
Branches 958 857 -101
==========================================
- Hits 9516 9440 -76
+ Misses 928 541 -387
|
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.
First pass, added few comments. Good job!
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 added few comments, and have some questions too.
Last thing: could you please add some screenshots how the spans look like (for example from zipkin or something relevant etc.) ?
packages/opentelemetry-plugin-http/test/functionals/utils.test.ts
Outdated
Show resolved
Hide resolved
b020813
to
61088a7
Compare
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.
Overall this looks ok, but I am very wary of the use of a mutilated request object. In my mind this not only has the chance to break a user's application (in the unlikely event they also try to set/modify a property with the same name), but makes the express plugin an implicit dependency of the http plugin. If someone unaware of this behavior modifies this plugin in the future and changes this property, it has the chance of breaking a seemingly unrelated non-dependent plugin.
02862b4
to
f92d939
Compare
edf3454
to
f56b7af
Compare
75dca3e
to
fe66b6f
Compare
Somehow getting 500 (Server Error) on codecov report. |
@OlivierAlbertini since you had a lot of comments I would appreciate your review here before merge |
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 just miss some screenshots to show how the spans will look like when using this plugin, other than that lgtm
@obecny i will add examples in a seperate PRs and include screenshot in there |
@vmarchaud I agree with mayur we should not have broken links in the readmes. We can add a link when there is an example to link to @mayurkale22 once he does that I think we should merge this. seems like @OlivierAlbertini is busy |
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.
Sorry for the delay, I will test with some internal apps this week-end. I will give feedback if needed.
@vmarchaud good job!
| `ignoreLayers` | `IgnoreMatcher[]` | Express plugin will not trace all layers that match. | | ||
| `ignoreLayersType`| `ExpressLayerType[]` | Express plugin will ignore the layers that match based on their type. | | ||
|
||
For reference, here are the three different layer type: |
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.
👍
49f61c2
to
639ca21
Compare
@dyladan I've rebased the PR and removed the link from the readme |
Co-authored-by: Rauno Viskus <[email protected]>
TODO:
http.route
in the http server span