-
Notifications
You must be signed in to change notification settings - Fork 4.5k
examples/opentelemetry: demonstrate enabling experimental metrics #8388
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
examples/opentelemetry: demonstrate enabling experimental metrics #8388
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8388 +/- ##
==========================================
- Coverage 82.33% 82.31% -0.03%
==========================================
Files 413 413
Lines 40454 40430 -24
==========================================
- Hits 33307 33278 -29
+ Misses 5782 5779 -3
- Partials 1365 1373 +8 🚀 New features to boost your workflow:
|
Please merge the latest master branch to unblock the PR Validation test. |
The merge is not performed correctly. The PR diff is showing all the commits that were merged. Can you please reset and do a regular |
0243437
to
e5de1e2
Compare
@arjan-bal I force-pushed after merging the latest master, and it seems the branch got closed automatically. Can you able to open this branch. |
There are 0 commits on the PR, so it can't be re-opened. If you can bring back the commits on this branch, I should be able to re-open it. |
0ea97fb
to
db6900c
Compare
db6900c
to
5143e0d
Compare
5143e0d
to
d2e8366
Compare
// These are example experimental gRPC metrics, which are disabled by default | ||
// and must be explicitly enabled. For the full, up-to-date list of metrics, | ||
// see: https://grpc.io/docs/guides/opentelemetry-metrics/#instruments |
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.
Please move these comments to the line just above Metrics:
.
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.
Done
// up-to-date list of metrics, see: | ||
// https://grpc.io/docs/guides/opentelemetry-metrics/#instruments | ||
Metrics: opentelemetry.DefaultMetrics().Add( | ||
"grpc.server.call.started", |
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.
why are we adding these in default? These are already part of default metric set
grpc-go/stats/opentelemetry/opentelemetry.go
Line 443 in bdbe6a2
defaultPerCallMetrics = stats.NewMetricSet(ClientAttemptStartedMetricName, ClientAttemptDurationMetricName, ClientAttemptSentCompressedTotalMessageSizeMetricName, ClientAttemptRcvdCompressedTotalMessageSizeMetricName, ClientCallDurationMetricName, ServerCallStartedMetricName, ServerCallSentCompressedTotalMessageSizeMetricName, ServerCallRcvdCompressedTotalMessageSizeMetricName, ServerCallDurationMetricName) |
Fixes #8311
RELEASE NOTES: