Automatic Instrumentation of Main Process for Performance Monitoring

[AbhiPrasad]

Add automatic instrumentation to track the performance of the main process. We can start off by instrumenting startup time, and then move on from there.

Open questions:

• How do we know when startup is done?
• What child spans do we attach to the transaction?
• What metrics do we automatically attach to the transaction?
• How do we link transactions that happen in the main process to the renderer? Do we even need to this?

[timfish]

One key metric is app startup time which will be from main process start to when the apps UI is displayed.

From the Electron main process we have access to process.uptime() to get the real start point and we can subscribe to the renderer dom-ready event to know when displaying the app is complete.

Alternatively, we could intercept the transaction from BrowserTracing and modify it to represent the entire app load rather than solely the browser front-end.

[AbhiPrasad]

Alternatively, we could intercept the transaction from BrowserTracing

We could also do away with BrowserTracing entirely if we feel like it has minimal value, and replace it with our own more opinionated version for the Electron renderer.

IMO I'd like it if the transaction represents then entire app load. We do this in mobile with a high degree of success.