Skip to content
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

Follow-up improvements from #2060 #2088

Merged
merged 2 commits into from
Feb 28, 2020
Merged

Follow-up improvements from #2060 #2088

merged 2 commits into from
Feb 28, 2020

Conversation

jpkrohling
Copy link
Contributor

Signed-off-by: Juraci Paixão Kröhling juraci@kroehling.de

Which problem is this PR solving?

@jpkrohling jpkrohling requested a review from a team as a code owner February 26, 2020 15:42
Copy link
Member

@yurishkuro yurishkuro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, but I really think the repetition of grpclog is unnecessary. We already initialize the Zap logged in Service, we should do the same for grpclog (and perhaps in the future change it to go through Zap instead of going directly to stdout).

@@ -50,6 +52,7 @@ func main() {
return err
}
logger := svc.Logger // shortcut
grpclog.SetLoggerV2(grpclog.NewLoggerV2(ioutil.Discard, os.Stderr, os.Stderr))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not do it somewhere in svc?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In fact, looks like it's there already!

grpcZap.ReplaceGrpcLogger(logger.WithOptions(
// grpclog is not consistent with the depth of call tree before it's dispatched to zap,
// but Skip(2) still shows grpclog as caller, while Skip(3) shows actual grpc packages.
zap.AddCallerSkip(3),
))

Just need to remove it from the mains then.

@codecov
Copy link

codecov bot commented Feb 27, 2020

Codecov Report

Merging #2088 into master will decrease coverage by 0.03%.
The diff coverage is 63.15%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2088      +/-   ##
==========================================
- Coverage   96.33%   96.29%   -0.04%     
==========================================
  Files         214      214              
  Lines       10537    10535       -2     
==========================================
- Hits        10151    10145       -6     
- Misses        328      331       +3     
- Partials       58       59       +1
Impacted Files Coverage Δ
cmd/collector/app/server/zipkin.go 0% <0%> (ø) ⬆️
cmd/flags/service.go 0% <0%> (ø) ⬆️
cmd/collector/app/server/http.go 0% <0%> (ø) ⬆️
cmd/collector/app/server/grpc.go 66.66% <100%> (-1.2%) ⬇️
cmd/collector/app/collector.go 72.15% <100%> (-1.02%) ⬇️
cmd/query/app/server.go 91.78% <0%> (-2.74%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 913ab1c...7c9afc5. Read the comment docs.

@jpkrohling
Copy link
Contributor Author

The Cassandra integration test is failing, but isn't apparently related to this PR. Master was showing the build as passing, but it failed with the same reason once I started the job again:

https://travis-ci.org/jaegertracing/jaeger/jobs/655134449

Copy link
Member

@yurishkuro yurishkuro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cassandra issues should be fixed in master

Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
@jpkrohling jpkrohling merged commit 2c6f405 into jaegertracing:master Feb 28, 2020
@jpkrohling jpkrohling deleted the Follow-up-from-2060 branch July 28, 2021 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants