Distinguish between session creation and execution in session info #1909
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Panel has supported recording information about user sessions for a while. In doing so it recorded three events, 'started', 'rendered' and 'ended'. However the 'started' event was really recording the time after the session had already been created and fully initialized. This adds a fourth key called
'launched'
, which records when the initial request arrives but before the dashboard script has been executed.This means that we can separately compute execution time (server-side) and time to render since initial request (client-side).