feat(api-metrics): rename metric instruments to match feature-freeze API specification#2496
Conversation
a8ae8cd to
53768bd
Compare
I can only guess what @legendecas logic is here, but my guess is that it is to have the least disruption to what people already know. JS already had I would prefer to go with the spec on this one though. We will be changing a lot of the metric spec anyway so there isn't a strong reason to keep what we have. |
|
@legendecas are you planning no making the suggested naming changes? |
|
@dyladan If people are ok with the |
# Conflicts: # experimental/packages/opentelemetry-exporter-otlp-grpc/protos # experimental/packages/opentelemetry-exporter-otlp-proto/protos # experimental/tsconfig.esm.json # experimental/tsconfig.json
pirgeo
left a comment
There was a problem hiding this comment.
Great Work! I just added a few nits, but all of these are personal preference, so please disregard as you see fit.
|
@pirgeo thanks for the review, updated! |
obecny
left a comment
There was a problem hiding this comment.
Some minor things and few missing, but I also found some replacement which should be different, not sure if that is a mistake then or you rearranged the order but then maybe it will be easier to revert just the order so the replacing will be covered with those for easier review
Synchronous
Counter -> Counter
UpDownCounter -> UpDownCounter
ValueRecorder -> Histogram
Asynchronous
SumObserver -> ObservableCounter
UpDownSumObserver -> ObservableUpDownCounter
ValueObserver -> ObservableGauge
Please update also Upgrade guidelines listing what has changed and what not
|
@obecny Reverted the reordering. Sorry for the inconvenience. Updated the PR with minor observable renaming. |
7187ad3 to
68f408e
Compare
This PR applies following renames regarding to the feature-freeze metrics API spec:
There is no functional change.