feat: Manual Tracing - Idle Transaction

[denrase]

Overview

Add a RouteObserver where transactions are started when new routes get pushed. They are finished after a fixed duration idle timer finished, when a new route is pushed, or when a route is popped.

It's mainly based on the feedback of you @ueman in #220 and your work here, thank you again!

Implementation

• Create a transaction when a new route is pushed.
• Finish previous transaction when a new one is pushed.
• Finish transactions automatically after three seconds. Child spans do not prolong this idle time.
• Transactions are only created when pushed, so the initial root transaction with name "/" is only started and finished once.

Other/Discussion

• Users would need to provide RouteSettings with a name parameter in MaterialPageRoute if this wer part of the SDK.
• Added a child span to multi step sync.
• Should we also re-start transactions when going back to a route?
• Should we handle Popups or Modals differently?
• Can't seem to find / main route on sentry.io. Is this an invalid name?
• Child operations/http calls that take longer than the idle timeout may not be be associated with the transaction.

Screenshots

[ueman]

Can't seem to find / main route on sentry.io. Is this an invalid name?

This is the initial route from here.

[denrase]

@ueman Yeah, but it doesn't show up for me on the projects performance page on sentry.io 🤔

[marandaneto]

Should we also re-start transactions when going back to a route?

it depends if it's in memory, how does it work on flutter? if everything is in memory, it's not worth re-starting, we don't on Android.

[marandaneto]

Child operations/http calls that take longer than the idle timeout may not be be associated with the transaction.

that would probably require the waitForChildren feature, since this is likely the case for most of the spans.

[marandaneto]

Should we handle Popups or Modals differently?

they could be spans from the current transaction (the view that is parent of the modal/popup), otherwise its own transaction

[marandaneto]

Added a child span to multi step sync.

can you elaborate? not sure that I understood the topic

[ueman]

Should we handle Popups or Modals differently?

they could be spans from the current transaction (the view that is parent of the modal/popup), otherwise its own transaction

That's what I've done here. In theory popups and modals are quite short lived, so it should be fine but in praxis I can imagine that there are quite a few long lived popups/models 🤷‍♂️