Operations | Monitoring | ITSM | DevOps | Cloud

This blog was co-authored by Justyn Roberts, Senior Solutions Consultant, PagerDuty Automation has become an integral piece in business practices of the modern organization. Oftentimes when folks hear “automation,” they think of it as a means to remove the manual aspect of the work and speed up the process; however, what lacks the spotlight is the value and return automation can offer to an organization, a team, or even just one specific process.

Zendesk provides support teams with an integrated solution for processing all types of customer inquiries and feedback. But as organizations scale, support tickets multiply, making it increasingly difficult to parse all of your customers’ feedback and time-consuming to investigate issues. Customers often report issues without providing the detailed context needed for troubleshooting, creating unclear and indirect paths to remediation.

For developers, understanding the performance of shipped code is crucial. Through the last decade, a tablestake function in software monitoring and observability solutions has been to save and track app metrics. Engineers love tools that get out of your way and just work, and the appeal of today’s best-in-class application performance monitoring (APM) suites lies in a seamless day zero experience with drop-in agent installs, button click integrations, and immediate metrics collection.

Do you have much experience using the Call Quality Dashboard (CQD)? Does your team go on about it being a ‘good starting point’? Do you even know what the CQD does? Fear not. If you answered ‘no’ to any of those questions, we’re going to fill you in with all the details that matter and give you some additional direction on how to get the most out of them. The bottom line is they’re a good starting point, but a long way from being a proactive performance solution.