1889347 - PoC: OpenTelemetry C++ based solution for exact tracing of failures

Status: RESOLVED FIXED

(Toolkit :: Gecko Trace, task)

Description

[Michael van Straten [:michael]]

This is a top level bug for including OpenTelemetry to enhance our tracing capabilities in gk.

Comment 1

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 - Merge commit '532a8080d0f4abb5633ecd84d8eb3a80cffa53e0' as 'third_party/opentelemetry-cpp'

Comment 2

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 part 3: Add IPC glue for opentelemetry-cpp types

Comment 3

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 part 5 - Tracing extensions for async primitives

Comment 4

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 - Instrumente Firefox using opentelemetry trace

Comment 5

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 part 2 - Vendor opentelemety-cpp library

Comment 6

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 - OpenTelemetry multithreaded tracing demo

Comment 7

[Michael van Straten [:michael]]

Attachment: Bug 1889347 - OpenTelemetry multiprocess tracing demo

Comment 8

[Mike Conley (:mconley) (:⚙️)]

Very interesting!

Hey jstutte,

This came up during General triage. We're not entirely sure what work this is for, and so aren't very sure which component it fits under. Is there a better fit than Toolkit :: General?

Comment 9

[Michael van Straten [:michael]]

Hey Mike,

I'm not the person you requested info from, but I have some insights into this.

We are in the process of submitting a proposal, which involves creating a bunch of proof of concept patches.
This component to seamed appropriate for the meta bug, since the proposed system would likely go under toolkits/components.
If it is too much of a burden to you guys to keep it here, we will move the meta bug to one of our own components.

Comment 10

[Jens Stutte [:jstutte]]

(In reply to Mike Conley (:mconley) (:⚙️) from comment #8)

Very interesting!

Hey jstutte,

This came up during General triage. We're not entirely sure what work this is for, and so aren't very sure which component it fits under. Is there a better fit than Toolkit :: General?

This touches various things, but Toolkit::General seems not to be the best place for this, indeed. I assume we should move this to XPCOM or MFBT but for now it is really just a PoC until we completely understand what we want to do. As this proposal came out from quota manager related work, we might want to keep it there until then.

Comment 11

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 part 4 - Introduce a new tracing component

Comment 12

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 part 5: Initialize tracers in XPCOM init

Comment 13

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 part 7: Traced Runnable extension

Comment 14

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 part 8: Traced MozPromise extension

Comment 15

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 part 1 - Add `moz.yaml` for vendoring opentelemetry-cpp

Comment 16

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 - Demo exporting OpenTelemetry data to Gecko Profiler

Comment 17

[Jari Jalkanen [:jari]]

Attachment: WIP: Bug 1889347 - Change MozPromise to track thread ping pong.

Comment 18

[Jari Jalkanen [:jari]]

Attachment: WIP: Bug 1889347 - Add TraceId and SpanId conversions to support Windows.

Comment 19

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 part 3 - Patch opentelemetry-cpp with mozbuild files

Comment 20

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 - Demo instrumentation of non-storage code

Comment 21

[Jan Varga [:janv]]

Attachment: Bug 1889347 - Extend Tracing Beyond Storage Modules - demo; r=#dom-storage

Comment 22

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1889347 - Test worst-case opentelemetry performance impact