Change Details

== Background We have been transitioning from using `desktopwebuiactions` and `mobilwwebuiactions` in the Event Platform to `web_ui_actions` in the Metrics Platform to align with our strategy of using MP as the future platform. Stopping use of desktop- and mobilewebuiactions will reduce technical debt and streamline our instrumentation, ensuring consistent and efficient data collection. This transition should not directly affect the end user and any current deliverables but will improve the overall performance and maintainability of our systems. == User story As an engineer, I want to retire `desktopwebuiactions` and `mobilwwebuiactions` and //only// use `web_ui_actions` in the Metrics Platform so that we can reduce technical debt and maintain a single source of instrumentation for UI actions. == Requirements - Deprecate desktopwebuiactions and mobilewebuiactions in the Event Platform. [X] Migrate all existing events from desktopwebuiactions to web_ui_actions in the Metrics Platform. - Ensure Web team metrics-related documentation is updated to reflect this change. - Communicate the change to relevant stakeholders, including everyone in Web team, #Data-Engineering Slack, Editing team, and look into any other teams have used this instrument in the past - Ensure that the sampling for this instrument is per session not per-pageview. === BDD - For QA engineer to fill out === Test Steps - For QA engineer to fill out == Design - No mockups required for this change as it is backend-related. == Acceptance criteria • Ensure the old schema desktopwebuiactions is deprecated and no longer fires. • To be safe, verify //again// that all events are now using the web_ui_actions schema in the Metrics Platform. • Update all relevant documentation to reflect the deprecation of desktopwebuiactions . • After this is done, make a ticket to monitor logstash to ensure the new setup is functioning as expected. == Communication criteria - An announcement should be made to the Web team about the deprecation of `desktopwebuiactions` and `mobilewebuiactions` and the transition to web_ui_actions. - Discussion should be initiated in the relevant project meetings to ensure everyone is aware of the change. == Rollback plan - If any issues arise during the transition, revert the events back to using desktopwebuiactions. --- This task was created by Version 1.0.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]]

== Background We have been transitioning from using `desktopwebuiactions` and `mobilwwebuiactions` in the Event Platform to `web_ui_actions` in the Metrics Platform to align with our strategy of using MP as the future platform. Stopping use of desktop- and mobilewebuiactions will reduce technical debt and streamline our instrumentation, ensuring consistent and efficient data collection. This transition should not directly affect the end user and any current deliverables but will improve the overall performance and maintainability of our systems. == User story As an engineer, I want to retire `desktopwebuiactions` and `mobilwwebuiactions` and //only// use `web_ui_actions` in the Metrics Platform so that we can reduce technical debt and maintain a single source of instrumentation for UI actions. == Requirements - Deprecate desktopwebuiactions and mobilewebuiactions in the Event Platform. [X] Migrate all existing events from desktopwebuiactions to web_ui_actions in the Metrics Platform. - Ensure Web team metrics-related documentation is updated to reflect this change. - Communicate the change to relevant stakeholders, including everyone in Web team, #Data-Engineering Slack, Editing team, and look into any other teams have used this instrument in the past - Ensure that the sampling for this instrument is per session not per-pageview. - Ensure that queries in all ongoing reporting (e.g. any monitoring dashboards, recurring reports) use the new data === BDD - For QA engineer to fill out === Test Steps - For QA engineer to fill out == Design - No mockups required for this change as it is backend-related. == Acceptance criteria • Ensure the old schema desktopwebuiactions is deprecated and no longer fires. • To be safe, verify //again// that all events are now using the web_ui_actions schema in the Metrics Platform. • Update all relevant documentation to reflect the deprecation of desktopwebuiactions . • After this is done, make a ticket to monitor logstash to ensure the new setup is functioning as expected. == Communication criteria - An announcement should be made to the Web team about the deprecation of `desktopwebuiactions` and `mobilewebuiactions` and the transition to web_ui_actions. - Discussion should be initiated in the relevant project meetings to ensure everyone is aware of the change. == Rollback plan - If any issues arise during the transition, revert the events back to using desktopwebuiactions. --- This task was created by Version 1.0.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]]

== Background We have been transitioning from using `desktopwebuiactions` and `mobilwwebuiactions` in the Event Platform to `web_ui_actions` in the Metrics Platform to align with our strategy of using MP as the future platform. Stopping use of desktop- and mobilewebuiactions will reduce technical debt and streamline our instrumentation, ensuring consistent and efficient data collection. This transition should not directly affect the end user and any current deliverables but will improve the overall performance and maintainability of our systems. == User story As an engineer, I want to retire `desktopwebuiactions` and `mobilwwebuiactions` and //only// use `web_ui_actions` in the Metrics Platform so that we can reduce technical debt and maintain a single source of instrumentation for UI actions. == Requirements - Deprecate desktopwebuiactions and mobilewebuiactions in the Event Platform. [X] Migrate all existing events from desktopwebuiactions to web_ui_actions in the Metrics Platform. - Ensure Web team metrics-related documentation is updated to reflect this change. - Communicate the change to relevant stakeholders, including everyone in Web team, #Data-Engineering Slack, Editing team, and look into any other teams have used this instrument in the past - Ensure that the sampling for this instrument is per session not per-pageview. - Ensure that queries in all ongoing reporting (e.g. any monitoring dashboards, recurring reports) use the new data === BDD - For QA engineer to fill out === Test Steps - For QA engineer to fill out == Design - No mockups required for this change as it is backend-related. == Acceptance criteria • Ensure the old schema desktopwebuiactions is deprecated and no longer fires. • To be safe, verify //again// that all events are now using the web_ui_actions schema in the Metrics Platform. • Update all relevant documentation to reflect the deprecation of desktopwebuiactions . • After this is done, make a ticket to monitor logstash to ensure the new setup is functioning as expected. == Communication criteria - An announcement should be made to the Web team about the deprecation of `desktopwebuiactions` and `mobilewebuiactions` and the transition to web_ui_actions. - Discussion should be initiated in the relevant project meetings to ensure everyone is aware of the change. == Rollback plan - If any issues arise during the transition, revert the events back to using desktopwebuiactions. --- This task was created by Version 1.0.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]]