WAS ResponseTimes: Disaggregate non-HTTP response times #302
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.
Confirmed that Dave is happy with this.
Previously, for ResponseTimes, non-HTTP work would be aggregated together into a
null
URI column. Instead, what this PR does is if it's non-HTTP work, then it sets the "URI" to the type of work (e.g. IIOP, MDB, etc.). This way we get response times disaggregated by the type of non-HTTP work and then this makes it easier to throw into a pivot table to break down response times of EJBs vs MDBs, etc.Example output: