Conversation
Codecov Report
@@ Coverage Diff @@
## master #227 +/- ##
==========================================
- Coverage 95.23% 95.21% -0.02%
==========================================
Files 92 100 +8
Lines 4767 4979 +212
Branches 492 517 +25
==========================================
+ Hits 4540 4741 +201
- Misses 227 238 +11
|
dyladan
left a comment
There was a problem hiding this comment.
First pass nothing looks bad. The structure of the RCAMetrics class is a little confusing to me, but after a little reading it seems fine.
dyladan
left a comment
There was a problem hiding this comment.
Seems fine to me. The implementation of metric.ts seems more complicated than I would expect and I would be worried implementing something this complex on top of our current metrics implementation because the sdk is so incomplete and the spec is changing so much. But in general nothing seems wrong.
mwear
left a comment
There was a problem hiding this comment.
LGTM. One question about the split between host and runtime metrics. Will it be possible to collect runtime metrics without collecting host metrics? I think this is use case that we'd like to support. The reason is that the OTel collector can generate host metrics, so some people will only want to generate runtime metrics from their applications.
| @@ -0,0 +1,61 @@ | |||
| #OpenTelemetry RCA Metrics for Node.js | |||
There was a problem hiding this comment.
| #OpenTelemetry RCA Metrics for Node.js | |
| #OpenTelemetry Host Metrics for Node.js |
There was a problem hiding this comment.
yes the runtime metrics do not generate host metrics.
Runtime Metrics are added on top of Host Metrics so PR is here to be able to see the differences easily:
obecny#1