Change Details

==== Problem Wikimedia Maps has the most number of outages at the foundation to date. As those outages occur, there is no defined performance metric to indicate success or service degradation; our current monitoring capabilities for maps are poor and unhelpful; and it is very complex and not easily understood in order to gain support and maintenance. ==== Hypothesis We believe that modernizing the maps infrastructure will reduce complexity and make adding , enable monitoring capabilities and better empower SRE to resolve issues quickly and intuitively. The plan is to approach this modernization iteratively and starting with replacing our current vector tile server, tilerator, with the open source vector tile server, Tegola. ==== Outcomes * An SLO is defined between Product Infrastructure and Site Reliability Engineering teams. * An SRE is able to resolve vector tile server issues without prior knowledge in less than 1 hour * Maintenance effort on vector-tile related outages reduces to 10% per quarter for a full-time engineer

==== Problem Wikimedia Maps has the most number of outages at the foundation to date. As those outages occur, there is no defined performance metric to indicate success or service degradation; our current monitoring capabilities for maps are poor and unhelpful; and it is very complex and not easily understood in order to gain support and maintenance. ==== Hypothesis //We believe that modernizing the maps infrastructure will reduce complexity, enable monitoring capabilities, and better empower SRE to resolve issues quickly and intuitively.// The plan is to approach this modernization iteratively and starting with replacing our current vector tile server, tilerator, with the open-source vector tile server, Tegola. We hope moving away from server-side raster rendering to client-side reducing dependency on SRE and allows this team to be autonomous when it comes to supporting and maintaining the maps stack. ==== Outcomes * An SLO is defined between Product Infrastructure and Site Reliability Engineering teams. * An SRE is able to resolve vector tile server issues without prior knowledge in less than 1 hour * Maintenance effort on vector-tile related outages reduces to 10% per quarter for a full-time enginee

==== Problem Wikimedia Maps has the most number of outages at the foundation to date. As those outages occur, there is no defined performance metric to indicate success or service degradation; our current monitoring capabilities for maps are poor and unhelpful; and it is very complex and not easily understood in order to gain support and maintenance. ==== Hypothesis //We believe that modernizing the maps infrastructure will reduce complexity and make adding , enable monitoring capabilities, enable monitoring capabilities and better empower SRE to resolve issues quickly and intuitively.// The plan is to approach this modernization iteratively and starting with replacing our current vector tile server, tilerator, with the open-source vector tile server, with the open source vector tile server,Tegola. TegolaWe hope moving away from server-side raster rendering to client-side reducing dependency on SRE and allows this team to be autonomous when it comes to supporting and maintaining the maps stack. ==== Outcomes * An SLO is defined between Product Infrastructure and Site Reliability Engineering teams. * An SRE is able to resolve vector tile server issues without prior knowledge in less than 1 hour * Maintenance effort on vector-tile related outages reduces to 10% per quarter for a full-time engineer