{"id":25255,"date":"2022-12-14T00:00:00","date_gmt":"2022-12-14T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/introducing-the-google-search-status-dashboard\/"},"modified":"2022-12-14T00:00:00","modified_gmt":"2022-12-14T00:00:00","slug":"introducing-the-google-search-status-dashboard","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/introducing-the-google-search-status-dashboard\/","title":{"rendered":"Introducing the Google Search Status Dashboard"},"content":{"rendered":"

Wednesday, December 14, 2022<\/p>\n

\n As we head into 2023, we want to introduce another tool for the public to understand the most
\n current status of systems which impact Search—crawling, indexing, and serving. While system
\n disruptions are extremely rare, we want to be transparent when they do happen. In the past, we’ve
\n worked with our
\n Site Reliability Engineers (SRE)<\/a> to
\n externalize these disruptions on our
\n Google Search Central Twitter<\/a>
\n account. Today, we’re introducing the
\n Google Search Status Dashboard<\/a>
\n to communicate the status of Search going forward.\n<\/p>\n

\n Over the past couple years we’ve been working with our SREs on improved ways to make information
\n about major incidents generally accessible and useful. The goal was to make reporting issues
\n quick, accurate, and easy. As a result, we have launched a new
\n status dashboard<\/a> and
\n simplified the process of communicating during incidents.\n<\/p>\n

\n This dashboard reports widespread issues occurring in the last 7 days, with some details and the
\n current status of the incident. A widespread issue means there’s a systemic problem with a
\n Search system<\/a> affecting a large
\n number of sites or Search users. Typically these kinds of issues are very visible externally, and
\n internally the
\n SREs’ monitoring and alerting mechanisms<\/a>
\n are working behind the scenes to flag the issues.\n<\/p>\n

\"The<\/p>\n

\n The dashboard has a number of features that you might already be aware of from other Google status
\n dashboards, such as an
\n RSS feed<\/a>
\n you can subscribe to and
\n view of historical data<\/a>.\n<\/p>\n

How we communicate incidents and updates<\/h3>\n

\n Once we confirm with SREs that there’s an ongoing, widespread issue in Search, we aim to post an
\n incident on the dashboard within an hour, and consecutive updates to the incident within 12 hours.
\n Unlike with a traditional automated dashboard, our global staff reports these updates. The start
\n time of the incident is generally when we managed to confirm the issue.\n<\/p>\n

\n Outside of the traditional status update you might see, we will also try to provide more
\n information that might resolve the solution. For example, in the hypothetical scenario that the
\n nameserver handling domain name resolution for millions of sites refuses Googlebot’s connection
\n requests, we may post an update saying that changing nameservers may mitigate the issue sites are
\n experiencing. Of course with any issue, we will keep posting updates to the incident—with
\n mitigation possibilities when available\u2014until the incident is resolved.\n<\/p>\n

\n We consider an incident resolved when our engineers have made changes that will end the impact on
\n the system. While this means that the system itself is now healthy, sites may experience effects
\n for some time until they’re reprocessed, depending on the type of incident.\n<\/p>\n

\n If you want to learn more about the dashboard, we have a
\n dedicated page for the Search Status dashboard<\/a>
\n on Google Search Central. If you want to leave some feedback about the dashboard, tweet at us
\n @googlesearchc<\/a>.\n<\/p>\n