== Background
As part of the Data Platform Product Vision and Roadmap for FY 23/24, the Metrics Platform Clients will be managed by a control layer UI (heretofore `Control Plane`) that will enable centralized administration of instrumentation, schemas, etc.
See Phases 3+4 of the [[ https://miro.com/app/board/uXjVPcitXco=/ | Data Platform Product Vision and Roadmap ]]
{F36865745}
== Metrics Platform control layer (web app) requirements (high level)
- Metrics Platform Clients can be used for easy instrumentation of events
- Centralized and consistent way to run experiments (AB Tests, MAB Tests etc).
- Control layer UI allows for centralized management of instrumentation schemas, including privacy and security enforcement.
- Custom Data can be configured from within the control layer
- Destination of where to write data can also be selected.
== Specific: What do we want to achieve?
Build a control plane interface for administering instrumentation of events using Metrics Platform client libraries.
== Measurable: How will we know when we've reached our goal?
When the UI is in production and end users can effectively dispatch events to specified streams by submitting a form.
== Achievable: What support will we need to achieve our goal?
[ ] Database for backend
[ ] Frontend interface for submitting events to specific streams
TK
== Relevant: Is this goal worthwhile?
As part of the improvement effort of WMF's infrastructure platform, the Metrics Platform Client libraries and an associated centralized management system will dramatically reduce the friction of rolling out instruments for feature management, A/B testing, experiments.