The ActivityTracer has some history that we should consider improving. Specifically, the activity instrumentation is responsible for generating telemetry (spans) that represent the application startup. Because this project is strongly geared at targeting RUM use cases, we have assumed that all "user monitored" apps will have a main activity, and that activity can be used for measuring/tracing application launch.
The assumption is probably fine, but mixing up or otherwise blending the ideas of "application start" and "activity state change" seems not great.
Do the two really need to be traced together? Is there a way we might split these apart by creating a new instrumentation to track app start? If we did that, could the activity state spans still be parented correctly?
We could also vastly improve the semantic conventions for all of these.
The ActivityTracer has some history that we should consider improving. Specifically, the activity instrumentation is responsible for generating telemetry (spans) that represent the application startup. Because this project is strongly geared at targeting RUM use cases, we have assumed that all "user monitored" apps will have a main activity, and that activity can be used for measuring/tracing application launch.
The assumption is probably fine, but mixing up or otherwise blending the ideas of "application start" and "activity state change" seems not great.
Do the two really need to be traced together? Is there a way we might split these apart by creating a new instrumentation to track app start? If we did that, could the activity state spans still be parented correctly?
We could also vastly improve the semantic conventions for all of these.