Integrating Traces and Logs with OpenTelemetry

Tracing is a great way to monitor your services, but how does one go about fixing latency issues in a specific service? In this episode of Stack Doctor, Yuri Grinshteyn shows you how to connect traces with logs via OpenTelemetry and Cloud Trace and Logging, enabling you to pinpoint and debug service latency issues in a snap!
Integrating Tracing and Logging with OpenTelemetry and Stackdriver → goo.gle/2X1vA56
Github → goo.gle/2XfUsGp
Check out other videos in this series → goo.gle/2M406XL
For latest releases, please subscribe to the GCP Channel → goo.gle/GCP
Product: Google Cloud Operation Suite, OpenTelemetry, Cloud Trace; fullname: Yuri Grinshteyn;
#StackDoctor

[@Gary21H]

Thanks Doctor. How would you go about doing this for multiple requests? For example, if there is an error on a checkout page, how could you find all traces made at each step of the session?

[@Pablo-nb8tx]

Hello, I have a question, when the free period ends, do they charge you something or when you are doing a project do they charge you something in between?

[@talpasternak538]

What about the parent span id? It is not shown in the log entry. How is the hierarchy of spans established from the logs?

[@dimitrisfinas6161]

Why not simply using the log events of the OpenTelemetry trace specification to directly add your logs to the span?

[@dcydrob]

I think log events wasn't around when the vid was made?

[@AdrianColley]

So, the context argument is the wrong context, and you have to use library routines to map it through a Span to the right context; and then, the right context is only used to get strings for span ID and trace ID. That's a very hairy API.