-
Notifications
You must be signed in to change notification settings - Fork 409
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: Added http timeslice metrics from otel #2924
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2924 +/- ##
==========================================
- Coverage 97.42% 97.38% -0.05%
==========================================
Files 316 316
Lines 48383 48406 +23
==========================================
+ Hits 47139 47140 +1
- Misses 1244 1266 +22
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
assert.equal(attrs['url.scheme'], 'http') | ||
assert.equal(attrs.nr_exclusive_duration_millis, duration) | ||
|
||
const unscopedMetrics = tx.metrics.unscoped |
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.
It's not clear to me if there should be any scoped
metrics. When I step through, there are not any.
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.
yes there are a lot of metrics getting created, some aren't complete because it's not propagating context from upstream if it exists(which I will add in my ticket) but here are some that need asserted:
Apdex
, Apdex/<partialName>
which is currently null(I have fixed this), HttpDispatcher, WebTransactionTotalTime
, WebTransactionTotalTime
/(i have fixed in my PR)
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.
Those are present in the unscoped
metrics. I can add assertions for them. But I get zero metrics in tx.metrics.scoped
.
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.
ah sorry, yea there are no scoped metrics in this recorder. you can tell by looking at the recorder, the 2nd arg would be the scope and all are set to null
assert.equal(attrs['url.scheme'], 'http') | ||
assert.equal(attrs.nr_exclusive_duration_millis, duration) | ||
|
||
const unscopedMetrics = tx.metrics.unscoped |
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.
yes there are a lot of metrics getting created, some aren't complete because it's not propagating context from upstream if it exists(which I will add in my ticket) but here are some that need asserted:
Apdex
, Apdex/<partialName>
which is currently null(I have fixed this), HttpDispatcher, WebTransactionTotalTime
, WebTransactionTotalTime
/(i have fixed in my PR)
f6dee73
to
7017def
Compare
7017def
to
98d57a4
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.
LGTM. i have work that's layering on top of this.
This PR resolved #2655.