AB#442741: add response_time to request logs
#32
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
njdullea
changed the title
response_time to request logs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Work Item URL
https://dev.azure.com/nintex/Nintex/_workitems/edit/442741
Description
In the Seaquill/Nautilus transition dashboard, we are adding a section to compare Seaquill request
response_time's to Nautilus requestresponse_time's. However, currently we only include theresponse_timein our Node service response logs.This PR updates our Golang spec request logs to include a calculated
response_time, similar to how we storeresponse_timefor Node response logs.Just to note, the Node services store a request and a response log, whereas our Golang services only store a request log.