From SLO to GOTY: How Actionable Alerts Lead to Adoring Fans (Presented by HoneyComb)

Your players aren’t interested in your CPU utilization, and nobody is starting Reddit threads about how much disk space you have available. Questions like, “How long will I be in this queue?” or “How many disconnects is that today?” draw the wrong kind of attention. Instead of trying to guess which of your system metrics have the potential to cause an issue, your tools need to evolve from asking the same kinds of questions that your users are. An SLO, or Service Level Objective, lets you do this, resulting in fewer false alarms and surprises. The result? Happier players, happier teams, and a more productive organization.