add ui.ttid to span operations #776
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@AbhiPrasad @marandaneto @philipphofmann |
| @@ -181,6 +181,7 @@ Serverless related spans are expected to follow OpenTelemetry's [Function as a S | |||
| | | app.start.cold | | | |||
| | ui | | An operation on a mobile UI | | |||
| | | ui.load | | | |||
| | | ui.ttid | | | |||
There was a problem hiding this comment.
Should that be part of app.start? or every screen would have its own ttid?
There was a problem hiding this comment.
every screen it's going to have its own ttid
we'll also add the ttfd (time to full display) to every screen, too, but that's for another pr
There was a problem hiding this comment.
I think we should mention what ttid stands for = time to initial display. Maybe we could also call it
ui.load.inital ui.load.full? Most developers won't understand what ttid stands for and they have to go to our docs.
There was a problem hiding this comment.
could be even ui.load.initial_draw and ui.load.full_draw. But I agree ttid is probably not well-known, so I'd also vote for changing it
There was a problem hiding this comment.
That would be semantically wrong I guess, initial_draw would mean it's drawn but that refers only to the very first frame only.
full_draw would mean it's fully drawn, but it's not only about drawing but rather waiting for async content and redrawing it.
so maybe initial_display and full_dislay? it's pretty much the wording for both acronyms
There was a problem hiding this comment.
so let's go with ui.load.initial_display and ui.load.full_display? These make sense to me
There was a problem hiding this comment.
@philipphofmann does it make sense to you on ios?
There was a problem hiding this comment.
Yes, that makes sense. I'm happier now with this name as it's self-explanatory.
|
@stefanosiano, please also add |
In this same pr? Shouldn't we wait after implementing it? |
|
I think it's OK to merge it already, even if we don't have the implementation. We have already decided on the name. We can always change the docs again. |
We are going to add a ttid (time to initial display) span to the automatic activity transactions.
The use case is mainly for mobile developers.
The current activity transaction duration is not reliable to have an understanding of how much time it took to actually load an activity, due to possible other spans added during the transaction.