Instrumenting a desktop application

[parched]

I'm wondering what would be the best way to instrument a desktop application I'm working on. It's a C# WinUI 3 app if that's relevant.
The life cycle of the app looks like this (simplified):

1. App start up
2. Wait around for interaction from the user which can be split into these two types
   • GUI navigation and form filling
   • Submit action (which does the "interesting" stuff)

I'm currently wrapping the submit actions in span which is the bit that seems clear to me.
I'm thinking next I should wrap the app start up in span.
But what I want to know is how I can create a relationship between everything that happens during the lifetime of the app. i.e,

• start up span
• action spans
• logs that happen during GUI navigation that aren't under an action span.

I have 3 ideas, but they don't seem great to me:

1. Create a root span that lasts the whole lifetime of the app - I don't think this will work because the root span will never end.
2. Link every action span to the start up span - this gets part way there, but doesn't capture the logs the live outside of the spans
3. Create some unique ID when the app starts and add that to every log and span - this might work but I'd have to figure how to inject that ID everywhere. I hoped there might be something more integrated in OpenTelemetry.

What's the recommend way of handling this situation?