Skip to content

tracing: Update docs to clarify situation with trace context propagation#1733

Merged
mattklein123 merged 1 commit intoenvoyproxy:masterfrom
objectiser:tracedoc
Sep 27, 2017
Merged

tracing: Update docs to clarify situation with trace context propagation#1733
mattklein123 merged 1 commit intoenvoyproxy:masterfrom
objectiser:tracedoc

Conversation

@objectiser
Copy link
Copy Markdown
Contributor

Copy link
Copy Markdown
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

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

Thanks @objectiser this looks great to me. Will defer to @adriancole on whether the text is OK.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

nit: reflow to ~100 col.

Copy link
Copy Markdown
Member

@rshriram rshriram left a comment

Choose a reason for hiding this comment

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

Minor nits on my end. Thanks for doing this!
LGTM

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

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...

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Oh you have described it here.. may be nice this part to the top? To start the paragraph with the crux of this discussion

@objectiser
Copy link
Copy Markdown
Contributor Author

@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.

@mattklein123
Copy link
Copy Markdown
Member

I don't have a strong opinion on additional moves. @objectiser can you merge master so the Circle tests get run?

@objectiser
Copy link
Copy Markdown
Contributor Author

@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.

Copy link
Copy Markdown
Member

@rshriram rshriram left a comment

Choose a reason for hiding this comment

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

This reads very well!

mattklein123
mattklein123 previously approved these changes Sep 26, 2017
Copy link
Copy Markdown
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

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

Very nice. Thank you for making the docs better.

Copy link
Copy Markdown

@bhs bhs left a comment

Choose a reason for hiding this comment

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

@objectiser two nits, neither of which I feel strongly about!

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

pedantic nitpick:

`binary "basictracer" < ... >` carrier

(OpenTracing per se does not have an "official" encoding here)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

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.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I've added LightStep (via OpenTracing API) - let me know if that is ok.

@mattklein123
Copy link
Copy Markdown
Member

@objectiser thanks LGTM. Can you merge master to fix release CI issue and also fix DCO?

mattklein123
mattklein123 previously approved these changes Sep 27, 2017
@objectiser
Copy link
Copy Markdown
Contributor Author

@mattklein123 Just noticed the remaining circleci jobs have been cancelled - is there a problem?

@mattklein123
Copy link
Copy Markdown
Member

Sorry please merge master again. Fixing CI issues.

@mattklein123 mattklein123 merged commit c52afae into envoyproxy:master Sep 27, 2017
costinm pushed a commit to costinm/envoy that referenced this pull request Oct 2, 2017
rshriram pushed a commit to rshriram/envoy that referenced this pull request Oct 30, 2018
* Update_Dependencies (envoyproxy#1657)

* Use mTLS mode enum to decide authentication result.

* Clang

* Use NOT_REACHED macros for default case.

* Clang
jpsim pushed a commit that referenced this pull request Nov 28, 2022
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>
jpsim pushed a commit that referenced this pull request Nov 29, 2022
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>
mathetake added a commit that referenced this pull request Mar 3, 2026
**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>
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.

RFC: Update the tracing docs to better explain options available to service developers

4 participants