adding baggage to whitepaper #202
Conversation
✅ Deploy Preview for tag-observability ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Guangya Liu <[email protected]>
| @@ -259,6 +260,17 @@ Profiling data produced by runtimes typically includes statistics down to the li | |||
|
|
|||
| > Image 2 shows an example icicle graph for a CPU profile of an application written in Go. It includes a kernel operation done by the Syscall call. This profile highlights that 35% of CPU time was used to compute hash, indicating potential optimization opportunities. [Source](https://pprof.me/9ce2c2d/). | |||
|
|
|||
| ### Baggage | |||
There was a problem hiding this comment.
I wonder, how is that a new signal vs trace detail? 🤔
There was a problem hiding this comment.
@bwplotka can you check https://opentelemetry.io/docs/concepts/signals/baggage/ ? From the documentation there, the baggage is a new signal at same level as trace, metrics and logs.
There was a problem hiding this comment.
I agree with @bwplotka
Though Baggage is at the same level as traces, metrics, and logs on the site, one of the first paragraphs mentions that Baggage is transferred alongside Context which can be attached to traces, metrics, or logs. Given it attaches to those three signal types, Baggage isn't separate from them.
No description provided.