Monitoring systems gather and log a wide range of performance data on a diverse range of targets—from applications to user experience, networks, servers, and more. Usually, monitoring is conducted under runtime conditions, but synthetic monitoring can also be used to simulate loads and test the resilience of web services, for example.
Today at PagerDuty Summit 2019, we announced PagerDuty for Customer Service—a powerful new way to connect Customer Service teams to engineering and IT teams. We were also excited to debut two new partner integrations with Zendesk and Salesforce Service Cloud, and we can’t wait to show users how PagerDuty and our customer service ecosystem partners help connect the right teams so they can work together and resolve issues quickly to reduce customer impact.
At PagerDuty, we continually innovate every month (check out our What’s New page for the latest updates). But while we ship product continuously, we also save a plethora of new and improved capabilities to share with our customers at PagerDuty Summit, our annual customer event.
Opsgenie was built by real people who truly understood the pain of on-call, alert fatigue, and collaboration roadblocks. We empower our customers to resolve incidents faster by leveraging the tools they already use. As part of our mission to keep your always-on services up and running, we’ve worked with three key partners to strengthen the integrations we offer. It’s important that during an incident you can use the tools you’re accustomed to.
Read the details on what's new in the design and we have news on 4 more StatusHub feature updates.
When PagerDuty’s VP of Product Management Rachel Obstler announced the beta version of our new Slack integration in April in her “Anticipating, Monitoring, and Managing Incidents via Slack” panel at Slack Frontiers, we expected significant interest in the integration among our customers.
I was reminiscing about an incident that happened at a past job with an old co-worker. You know the one, the one where you installed a library that makes some task of yours simple, only to reveal the library makes things worse. This incident in particular involved the way that images served out of our Ruby on Rails application, and the library that made it possible to “easily resize before serving” them.
An integral lesson every business (of any size) learns is that failure is inevitable at some point in the production cycle. There might be times where things go haywire at critical junctures sending teams scrambling to rectify the root issue and reinstate service. The underlying causes are often many and varied especially in large scale systems with complex architecture and interdependence.
