We want to be able to trace a remote debugging session from starting about:debugging to opening toolboxes and using the toolboxes to debug a target. To tie all the events together, we need to forward the session id of about:debugging to individual toolboxes created for remote debugging.

See more details in Bug 1504173 comment 6.

Tim, Harald: My initial idea was to reuse the session_id created when opening about:debugging for all the toolboxes opened from about:debugging.

However, if we imagine that a user starts to debug a tab with about:debugging and then later wants to debug an addon, this means that both toolbox "sessions" would have the same session_id. And we wouldn't be able to distinguish what the user used to debug the tab or the addon.

With that, I am thinking that we should still forward the about:debugging session_id to the toolboxes, but we should record it as an additional field, not as the session_id. Maybe opener_id, opener_session_id? Does this seem ok to you?

Yes, I think that sounds fine -- it makes sense for the session_id to be specific to the debugging session, if you'd like to learn about the journey through each debugging session.

I think it will probably be difficult to use Amplitude to connect the opener to the toolbox sessions but with the opener_id strategy you're describing, we could do a "manual" analysis pretty easily to count e.g. the number/variety of actions people take after opening about:debugging.

Agreeing with Tim (and forgot to un-ni me)