Log migration per-query information in a structured format
What does this MR do?
During migration testing, log a json file per migration with details of the individual queries executed during that migration.
Specifically, this includes:
- The sql text of each query
- any bind parameters
- start time
- end time
This data will support gitlab-org/database-team/team-tasks#147 (closed), which needs per-query timing information to create charts of query runtimes over the course of the migration, and details of the query text and bind parameters to report on queries with anomalous runtimes for specific parameter choices.
Screenshots (strongly suggested)
Here's a log from a test migration done by the pipeline that doesn't have any bind parameters: 20210604233157-query-details.json
Here's one from a test migration that I wrote locally that has a few queries with bind parameters: 20210615154212-query-details.json
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Edited by Simon Tomlinson