Switch Mixer tracing package to use jaeger library.#1693
Switch Mixer tracing package to use jaeger library.#1693istio-merge-robot merged 7 commits intoistio:masterfrom
Conversation
|
/retest all |
mandarjog
left a comment
There was a problem hiding this comment.
What is the behavior of jaeger http collector on a slow outbound transport? We have to ensure that spans are discarded correctly.
There was a problem hiding this comment.
Why change command line params?
Can we keep traceOutput to mean zipkin and only add a new flag for Jaeger.
There was a problem hiding this comment.
A couple of concerns:
traceOutputwas badly overloaded before- it implies a default stance towards zipkin, which I don't think we necessarily want
- i think
traceOutputmakes it less obvious what the flag value should be
Is your concern backwards compatibility of YAMLs? If so, one option would be to maintain support for traceOutput, mark it as deprecated, and do the value conversion in server.go.
There was a problem hiding this comment.
Yes, backwards compat for yamls and the command line options in general.
Let us make traceOutput an alias to zipkin then and mark as deprecated.
There was a problem hiding this comment.
Added alias and deprecation.
mixer/pkg/pool/goroutine.go
Outdated
There was a problem hiding this comment.
added to comment.
mixer/cmd/server/cmd/server.go
Outdated
There was a problem hiding this comment.
We should use standard url format instead.
zipkin://user:pass@host
There was a problem hiding this comment.
fwiw, this is not how the backend libraries take the args. So this would mean additional parsing on our part. Another potential consideration: USER and PASS mounted as secrets. Thoughts?
There was a problem hiding this comment.
removed basic auth support altogether -- it was kinda ugly (prefer Istio for securing access). we can add it back if needed later.
mixer/cmd/server/cmd/server.go
Outdated
There was a problem hiding this comment.
standard url for jaeger.
7aea417 to
2024105
Compare
|
PTAL. |
|
@jmuk can you ensure that this branch has the good memory characteristics that we fixed for openzipkin-go ? If that checks out this is great. |
|
Tried a bit, I don't see any memory issues like the ones in openzipkin-go. |
|
Note that with this PR we are using a an actively developed library that support both Jaeger and zipkin. This is great! /lgtm |
|
/retest all |
|
/retest |
1 similar comment
|
/retest |
|
/retest |
2024105 to
9ae7567
Compare
|
/lgtm cancel //PR changed after LGTM, removing LGTM. @douglas-reid @mandarjog |
e9e14a2 to
2384adc
Compare
Codecov Report
@@ Coverage Diff @@
## master #1693 +/- ##
==========================================
- Coverage 81.23% 81.17% -0.07%
==========================================
Files 191 185 -6
Lines 19344 18804 -540
==========================================
- Hits 15715 15264 -451
+ Misses 3173 3113 -60
+ Partials 456 427 -29
Continue to review full report at Codecov.
|
|
/test e2e-smoke |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
9878a64 to
df9b289
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mandarjog The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
/test all [submit-queue is verifying that this PR is safe to merge] |
|
Automatic merge from submit-queue. |
Automatic merge from submit-queue. Switch Mixer tracing package to use jaeger library. **What this PR does / why we need it**: This PR switches Mixer from using the openzipkin tracing library to the jaeger tracing library for tracing Mixer functions. This switch accomplishes a few key items: - Adds Mixer support for Jaeger backends - Removes the need for a custom fork of the OpenZipkin library - Adds better flag support for tracing control - Enables development of Jaeger adapter (library conflict with OpenZipkin library). It deprecates the `--traceOutput` flag and replaces it with several additional flags: - `zipkinURL`, - `jaegerURL` - `logTraceSpans` **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # Fixes istio/old_mixer_repo#1352 **Special notes for your reviewer**: **Release note**: ```release-note Add Jaeger support to Mixer. ```
What this PR does / why we need it:
This PR switches Mixer from using the openzipkin tracing library to the jaeger tracing library for tracing Mixer functions.
This switch accomplishes a few key items:
It deprecates the
--traceOutputflag and replaces it with several additional flags:zipkinURL,jaegerURLlogTraceSpansWhich issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #Fixes istio/old_mixer_repo#1352
Special notes for your reviewer:
Release note: