Change Details

**Objective**: To analyze the quality of the data collected with the updated Metrics Platform-based Wikilambda instrument by comparing that data to the data collected with the existing "monoschema" Wikilambda instrument and verify whether the migration to Metrics Platform can proceed or if there are any issues that need to be resolved. ## Prerequisites for data QA - [X] Mapping of old instrumentation to new instrumentation: - https://docs.google.com/spreadsheets/d/1WiPR-uzGlJ2LJ5DKks3WYRGV0W2uOl6l2WqwfdqZbrc/edit#gid=362321310 - This is primarily driven by engineer performing the migration - Analyst reviews map for completeness and correctness, and contributes/assists as needed - [X] Specific QA needs have been identified and are agreed upon - [] Analyst decides in collaboration with engineers/PM whether to QA the whole instrument, or if there are key parts that should be QAed and the rest can be assumed to be okay. - [] Document the parts and the relevant queries: - (1) overall counts by action and sub-action (if applicable) - **if relevant** (2) counts by specific identifiers (e.g. by session) - **NOTE**: these queries will almost always be limited by time in some way - [] New instrument has been deployed and activated (<link to phab task>) - [] Engineer has verified that events are flowing in and that the instrument is not producing schema validation errors. - [] Verify that events are flowing in: - [] EventGate Grafana dashboard - [] Kafka by Topic Grafana dashboard - [] EventStreams - [] New instrument doesn't have any schema validation errors - [] Prioritization agreement between analyst & PM of the QA work in the context of other needs/requests (e.g. PM may need to wait longer for some analysis so that the analyst can do the QA work) - [] Documentation of old and new table names and date of deployment for analyst's reference: | Instrument | Table name | Stream deployed (if applicable) | |------------|------------|---------------------------------| | Old | <name of table with data to compare to> | N/A | | New | <name of table with data to compare> | <YYYY-MM-DD> | ## Data QA checklist If more than one instrument is being migrated, these steps need to be completed for each one. - [] Count the daily number of schema validation errors for - [] Old instrument - [] New instrument - [] Compare counts of events by action and sub-action (as defined in the mapping from prerequisites) - [] **if relevant** Compare counts by specific identifier (as defined in the prerequisites) - [] Upload QA notebooks to Gitlab, making sure to follow [[ https://foundation.wikimedia.org/wiki/Legal:Data_publication_guidelines | data publication guidelines ]] - [] Document any issues (or notable observations found) on this ticket - [] Resolve this ticket **NOTE**: If any issues were identified that require fixing the new instrument, data QA of the fixed instrument will need to be filed as a new Phab task. Some of the checked prerequisites will carry over.

**Objective**: To analyze the quality of the data collected with the updated Metrics Platform-based Wikilambda instrument by comparing that data to the data collected with the existing "monoschema" Wikilambda instrument and verify whether the migration to Metrics Platform can proceed or if there are any issues that need to be resolved. ## Prerequisites for data QA - [X] Mapping of old instrumentation to new instrumentation: - https://docs.google.com/spreadsheets/d/1WiPR-uzGlJ2LJ5DKks3WYRGV0W2uOl6l2WqwfdqZbrc/edit#gid=362321310 - This is primarily driven by engineer performing the migration - Analyst reviews map for completeness and correctness, and contributes/assists as needed - [X] Specific QA needs have been identified and are agreed upon - [X] Analyst decides in collaboration with engineers/PM whether to QA the whole instrument, or if there are key parts that should be QAed and the rest can be assumed to be okay. - [X] Document the parts and the relevant queries: - (1) overall counts by action and sub-action (if applicable) - (2) counts by specific identifiers (e.g. by activity and browser session) - **NOTE**: these queries will almost always be limited by time in some way - [x] New instrument has been deployed and activated (<link to phab task>) - [] Engineer has verified that events are flowing in and that the instrument is not producing schema validation errors. - [] Verify that events are flowing in: - [] EventGate Grafana dashboard - [] Kafka by Topic Grafana dashboard - [] EventStreams - [X] New instrument doesn't have any schema validation errors - [X] Prioritization agreement between analyst & PM of the QA work in the context of other needs/requests (e.g. PM may need to wait longer for some analysis so that the analyst can do the QA work) - [X] Documentation of old and new table names and date of deployment for analyst's reference: | Instrument | Table name | Stream deployed (if applicable) | Instrumentation Task| |------------|------------|---------------------------------|--------| | Old | event.wikifunctions_ui | 2023-07-26 | T297511 | New | event.mediawiki_product_metrics_wikifunctions_ui | <2024-04-11> | T350497| ## Data QA checklist If more than one instrument is being migrated, these steps need to be completed for each one. - [] Count the daily number of schema validation errors for - [] Old instrument - [] New instrument - [] Compare counts of events by action and sub-action (as defined in the mapping from prerequisites) - [] **if relevant** Compare counts by specific identifier (as defined in the prerequisites) - [] Upload QA notebooks to Gitlab, making sure to follow [[ https://foundation.wikimedia.org/wiki/Legal:Data_publication_guidelines | data publication guidelines ]] - [] Document any issues (or notable observations found) on this ticket - [] Resolve this ticket **NOTE**: If any issues were identified that require fixing the new instrument, data QA of the fixed instrument will need to be filed as a new Phab task. Some of the checked prerequisites will carry over.

**Objective**: To analyze the quality of the data collected with the updated Metrics Platform-based Wikilambda instrument by comparing that data to the data collected with the existing "monoschema" Wikilambda instrument and verify whether the migration to Metrics Platform can proceed or if there are any issues that need to be resolved. ## Prerequisites for data QA - [X] Mapping of old instrumentation to new instrumentation: - https://docs.google.com/spreadsheets/d/1WiPR-uzGlJ2LJ5DKks3WYRGV0W2uOl6l2WqwfdqZbrc/edit#gid=362321310 - This is primarily driven by engineer performing the migration - Analyst reviews map for completeness and correctness, and contributes/assists as needed - [X] Specific QA needs have been identified and are agreed upon - [X] Analyst decides in collaboration with engineers/PM whether to QA the whole instrument, or if there are key parts that should be QAed and the rest can be assumed to be okay. - [X] Document the parts and the relevant queries: - (1) overall counts by action and sub-action (if applicable) - **if relevant** (2) counts by specific identifiers (e.g. by activity and browser session) - **NOTE**: these queries will almost always be limited by time in some way - [x] New instrument has been deployed and activated (<link to phab task>) - [] Engineer has verified that events are flowing in and that the instrument is not producing schema validation errors. - [] Verify that events are flowing in: - [] EventGate Grafana dashboard - [] Kafka by Topic Grafana dashboard - [] EventStreams - [X] New instrument doesn't have any schema validation errors - [X] Prioritization agreement between analyst & PM of the QA work in the context of other needs/requests (e.g. PM may need to wait longer for some analysis so that the analyst can do the QA work) - [X] Documentation of old and new table names and date of deployment for analyst's reference: | Instrument | Table name | Stream deployed (if applicable) | Instrumentation Task| |------------|------------|---------------------------------|--------| | Old | <name of table with data to compare to> | N/A |event.wikifunctions_ui | 2023-07-26 | T297511 | New | <name of table with data to compare>event.mediawiki_product_metrics_wikifunctions_ui | <YYYY-MM-DD> |2024-04-11> | T350497| ## Data QA checklist If more than one instrument is being migrated, these steps need to be completed for each one. - [] Count the daily number of schema validation errors for - [] Old instrument - [] New instrument - [] Compare counts of events by action and sub-action (as defined in the mapping from prerequisites) - [] **if relevant** Compare counts by specific identifier (as defined in the prerequisites) - [] Upload QA notebooks to Gitlab, making sure to follow [[ https://foundation.wikimedia.org/wiki/Legal:Data_publication_guidelines | data publication guidelines ]] - [] Document any issues (or notable observations found) on this ticket - [] Resolve this ticket **NOTE**: If any issues were identified that require fixing the new instrument, data QA of the fixed instrument will need to be filed as a new Phab task. Some of the checked prerequisites will carry over.