Introduce ExecutionMetadata model to capture execution level metrics in task and taskresult #545
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.
Pull Request type
NOTE: Please remember to run
./gradlew spotlessApplyto fix any format violations.Changes in this PR
Introduced ExecutionMetadata for Task and TaskResults entity to capture NEW operational metadata not already present in Task/TaskResult models
ExecutionMetadata includes - serverSendTime, clientSendTime, executionStartTime, executionEndTime, clientSendTime, pollNetworkLatency, updateNetworkLatency, additionalContext
Adding this execution metadata into task and taskResult which then be used by worker and server to set execution values.
Alternatives considered
Describe alternative implementation you have considered