-
Notifications
You must be signed in to change notification settings - Fork 55
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
docs: Documentation update for OpenTelemetry #915
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,20 @@ | ||||||
Automatic Trace/Span ID Extraction | ||||||
================================== | ||||||
|
||||||
The Google Cloud Logging library can automatically populate `LogEntry fields <https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry>`_ | ||||||
`trace`, `span_id`, and`trace_sampled` via OpenTelemetry integration, or extracting header information from an HTTP request. | ||||||
|
||||||
OpenTelemetry Integration | ||||||
------------------------- | ||||||
|
||||||
If you have the OpenTelemetry SDK package installed and are logging from within an active OpenTelemetry span, that log entry will automatically | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit the SDK is not technically necessary here. Does this suggestion make sense to you? I think it's a little more precise
Suggested change
|
||||||
have the `trace`, `span_id`, and `trace_sampled` fields populated with metadata from that span. More information about OpenTelemetry can be found | ||||||
gkevinzheng marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
`here <https://opentelemetry.io/docs/languages/python/>`_. | ||||||
|
||||||
HTTP headers | ||||||
------------ | ||||||
|
||||||
Another possible method of automatic `trace`/ `span_id` is via extraction from HTTP headers. This feature requires a :doc:`supported Python web framework </web-framework-integration>`. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we want to mention that this is prioritized after OpenTelemetry? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think that's probably a good idea. |
||||||
Trace information is automatically populated from either the `W3C Traceparent <https://www.w3.org/TR/trace-context>`_ | ||||||
or `X-Cloud-Trace-Context <https://cloud.google.com/trace/docs/trace-context#legacy-http-header>`_ headers. | ||||||
Populating trace information this way also automatically populates the `http_request` field in the `LogEntry` as well. |
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.
Somehow and
trace_sampled
is not rendered correctly in the screenshot.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.
Looks like there's a space needed between "and" and "
trace_sampled
".