tracing: Update docs to clarify situation with trace context propagation#1733
tracing: Update docs to clarify situation with trace context propagation#1733mattklein123 merged 1 commit intoenvoyproxy:masterfrom
Conversation
0e18032 to
a421690
Compare
mattklein123
left a comment
There was a problem hiding this comment.
Thanks @objectiser this looks great to me. Will defer to @adriancole on whether the text is OK.
docs/intro/arch_overview/tracing.rst
Outdated
rshriram
left a comment
There was a problem hiding this comment.
Minor nits on my end. Thanks for doing this!
LGTM
docs/intro/arch_overview/tracing.rst
Outdated
There was a problem hiding this comment.
Nit: inbound and outbound instead of ingress vs egress. But if you feel that this correlates better with the ingress and egress operations, then leave it be.
docs/intro/arch_overview/tracing.rst
Outdated
There was a problem hiding this comment.
Services can emit additional traces over the standard traces emitted by Envoy. However, it is the responsibility of the service to transport these traces to the trace collector...
docs/intro/arch_overview/tracing.rst
Outdated
There was a problem hiding this comment.
Oh you have described it here.. may be nice this part to the top? To start the paragraph with the crux of this discussion
|
@rshriram I've just applied the minor changes for now - if others also think the use of tracer in the service should be moved above the manual propagation, then I've no problem switching it around. |
1e429a8 to
f52c823
Compare
|
I don't have a strong opinion on additional moves. @objectiser can you merge master so the Circle tests get run? |
9415510 to
001f191
Compare
|
@rshriram I've reorganized the section to put the discussion on use of tracer in the service first, followed by manual propagation - but on re-reading your comment I think I misinterpreted your suggestion. Could you have a quick review of this change and let me know your thoughts? The reason I originally put the emphasis on use of tracer in service for context propagation is that was the focus of this section of the doc - but the additional benefit is that it also enables the service to provide additional tracing information. |
mattklein123
left a comment
There was a problem hiding this comment.
Very nice. Thank you for making the docs better.
bhs
left a comment
There was a problem hiding this comment.
@objectiser two nits, neither of which I feel strongly about!
There was a problem hiding this comment.
pedantic nitpick:
`binary "basictracer" < ... >` carrier
(OpenTracing per se does not have an "official" encoding here)
There was a problem hiding this comment.
This text was in the original version - I was actually thinking about removing it as the service developer does not need to know anything about the format.
I'll remove and if anyone has any objections, I can add some modified text back.
docs/intro/arch_overview/tracing.rst
Outdated
There was a problem hiding this comment.
nit: ... outbound requests. (Note: for LightStep, the above is accomplished via OpenTracing; there should be no need to invoke LightStep's tracer directly for extraction or injection of context state) This approach would ...
(Or any other edit that makes it clear that LightStep's tracer is abstracted underneath OpenTracing's API)
There was a problem hiding this comment.
I've added LightStep (via OpenTracing API) - let me know if that is ok.
|
@objectiser thanks LGTM. Can you merge master to fix release CI issue and also fix DCO? |
236c4ff to
82a1e29
Compare
|
@mattklein123 Just noticed the remaining circleci jobs have been cancelled - is there a problem? |
|
Sorry please merge master again. Fixing CI issues. |
resolves envoyproxy#1711 Signed-off-by: Gary Brown <gary@brownuk.com>
82a1e29 to
c22c6d5
Compare
…ion (envoyproxy#1733) resolves envoyproxy#1711 Signed-off-by: Gary Brown <gary@brownuk.com>
* Update_Dependencies (envoyproxy#1657) * Use mTLS mode enum to decide authentication result. * Clang * Use NOT_REACHED macros for default case. * Clang
Description: This adds a dumpStats function to the Engine interfaces, allowing callers to retrieve the value of all active stats. This is done by invoking an admin handler, and so this PR also sets up a pattern for synchronously calling the admin handler. This should make it easier to add support for other features that would be based on invoking admin endpoints. Risk Level: Medium Testing: New integration tests Docs Changes: n/a Release Notes: n/a Signed-off-by: Snow Pettersen <snowp@lyft.com> Signed-off-by: JP Simard <jp@jpsim.com>
Description: This adds a dumpStats function to the Engine interfaces, allowing callers to retrieve the value of all active stats. This is done by invoking an admin handler, and so this PR also sets up a pattern for synchronously calling the admin handler. This should make it easier to add support for other features that would be based on invoking admin endpoints. Risk Level: Medium Testing: New integration tests Docs Changes: n/a Release Notes: n/a Signed-off-by: Snow Pettersen <snowp@lyft.com> Signed-off-by: JP Simard <jp@jpsim.com>
**Description** All directory under tests/ have exactly one corresponding Make recipe except for this one, so this moves it under the correct tests/data-plane-mcp. Plus the directory name was too broad as it's only for MCP, not AI data plane path. --------- Signed-off-by: Takeshi Yoneda <t.y.mathetake@gmail.com>
resolves #1711
@mattklein123 @adriancole @bhs @louiscryan