Fixup Net::HTTP breadcrumb url & span creation when Net::HTTP.start is used#1637
Fixup Net::HTTP breadcrumb url & span creation when Net::HTTP.start is used#1637st0012 merged 2 commits intogetsentry:masterfrom
Net::HTTP breadcrumb url & span creation when Net::HTTP.start is used#1637Conversation
|
CI failure is unrelated and I will update changelog with PR number anyway, so sending to review. |
|
OTOH breadcrumbs are already limiting max message size since https://github.com/getsentry/sentry-ruby/pull/1465/files, so limiting body size could be dropped |
|
@ojab thanks for the PR. I think they're both good additions but we can't add those information directly as it may contain pii data. we should only add them when sentry-ruby/sentry-ruby/lib/sentry/interfaces/request.rb Lines 40 to 44 in efcf170 |
|
Yeah, I saw that and guessed that only incoming stuff is counted as PII. |
2647b75 to
93910fc
Compare
|
Updated, CI is green. |
|
Also pushed commit to fix tracing of multiple requests in a single connection. |
6cff752 to
33de2cf
Compare
|
@ojab it looks like you've made a few other changes to address different issues? since you're essentially rewriting the |
|
also, the feature and fixes will likely go out separately (feature in |
7d29d36 to
6a03061
Compare
Net::HTTP breadcrumb url and add query string & body thereNet::HTTP breadcrumb url & span creation when Net::HTTP.start is used
6a03061 to
dacc310
Compare
|
Left only bugfixes in this PR and moved query string & body addition to the new PR #1642. Every change is split per-commit, so hope two PRs are ok. |
Codecov Report
@@ Coverage Diff @@
## master #1637 +/- ##
=======================================
Coverage 98.45% 98.45%
=======================================
Files 135 135
Lines 7505 7511 +6
=======================================
+ Hits 7389 7395 +6
Misses 116 116
Continue to review full report at Codecov.
|
|
Hey, any changes to be done here? |
|
@ojab hey sorry I'm quite busy recently so haven't got time to check all the PRs yet. |
Please keep these instructions in mind so we can review it more efficiently:
Right now we're not recording URL and creating single span for all the requests.
Description
Not sure if body addition is a welcome change and if 100 is a good length, but it would be useful for us.