The PagerDuty Incident Response Process is a detailed document that provides a framework for how to structure your incident response process. But sometimes it helps...by George Miranda
June 20, 2019
We kick off the July partner spotlight with FreshService, Instana and PepperData! Each partner brings something unique to the table and we’re excited to have them on board. Read on to learn a bit about each and how they’ve integrated with PagerDuty to deliver a better incident management solution.
Streamline Your Processes
From outages to security issues, there are a lot of things that can go awry in the development lifecycle. Ultimately, it falls upon the developer to ensure availability of the application by staying on top of incidents as they occur. Even with IT monitoring tools in place, it’s fairly easy to miss certain issues, and easier still to prioritize the not-so-urgent tickets over the critical ones.
Now you can count on Freshservice and PagerDuty to enhance your incident management process. Whether you’ve already been using PagerDuty or you just want an optimized experience while using Freshservice, our integration lets you consolidate, monitor, and prioritize major incidents.
All your incidents get recorded as they happen so you can easily and quickly take action from a centralized location – without toggling between tools and prolonging resolution times. You also get to create rules and set the escalation policy with every incident, which automatically sends the ticket to the right person, depending on the type and impact of ticket.
Your DevOps teams’ lives just got a whole lot simpler with the on-call scheduling feature as well – this lets teams focus on the actual resolution process instead of worrying about finding the right person to tend to alerts.
Teams get notified of all actionable alerts, instantly, via different channels – SMS, email, phone call, and even push notification through the Freshservice mobile app. You can now work in peace knowing that the Freshservice – PagerDuty integration ensures you’ll always be in the loop about any disruptions to your services.
Dramatically Reduce Noise
Instana and PagerDuty share a common goal. Both companies strive to reduce noise by precisely and efficiently informing DevOps about operational IT challenges in an actionable way, by communicating the right information to the right person at the right time while filtering noise.
PagerDuty has certainly found the right balance when it comes to managing and routing actionable notifications to DevOps and ITOps teams to ensure an incident management response. However, monitoring systems can generate a flood of alerts if not set up properly, effectively over-communicating that there is a problem. This is a challenge for traditional monitoring solutions. The architecture and operating model of modern dynamic applications in which development teams work are constantly changing. This forces ops teams to manually adjust the rules engines driving the alerting systems, with the inevitable consequence that the rules driving the monitoring systems are out of date. When something goes wrong, a storm of alerts gets pushed to PagerDuty, but the root cause may be unclear.
Instana tackles this issue by taking a completely new approach to monitoring. Simply put, the Instana team believes that you can’t monitor what you can’t model. Their secret to minimizing alert storms is to automatically construct a comprehensive model of the whole application architecture. Operating on the belief that any modern monitoring solution must be completely self-maintaining and automatic, Instana requires zero configuration. Moreover, they believe that as systems have become so complex, monitoring tools should actually assist DevOps teams with suggestions on how to optimize and fix issues.
Instana proudly integrates with PagerDuty so that customers continue to reliably receive notifications from across their monitoring stacks for effective incident management, while enjoying a dramatic reduction in noise.
To get started, check out the Instana Integration Guide.
More Granular Alerts
Although Pepperdata software automatically takes care of most Hadoop performance issues – such as preventing rogue apps from stomping on mission-critical apps – a notification about these events can be the difference between getting ahead of a problem and falling far behind it. This is especially true for certain instances that require human intervention to fix, like bad network cards, failing disks, or other broken hardware.
Proactive alerting is essential for guaranteeing maximum cluster performance because it allows for problem resolution sooner rather than later, and can alert the right developer to have code fixed before an issue arises. Sometimes, users just want to be aware of the adaptive management Pepperdata is doing on their behalf, and alerts are a great way to stay on top of what’s going on in your environment.
Customers use Pepperdata’s software to capture global knowledge of each cluster and enforce peak performance based on user-defined priorities and current cluster conditions. Pepperdata’s Adaptive Performance Core™ uses real-time processing to observe and reshape application usage of CPU, RAM, network, and disk second by second to deliver quality service for all jobs – solving many common Hadoop challenges automatically. For the times when you need to be alerted that something’s about to go wrong, Pepperdata’s integration with PagerDuty.
Now, Pepperdata users can turn any of 300+ metrics into an alert through PagerDuty with just a few clicks. An alert can be defined at any level of granularity – cluster, node, user, queue, job, or task – and at any threshold that makes sense for your business. By using the Pepperdata API to send alerts to PagerDuty, operators gain a deeper understanding of the cluster quickly and efficiently from the PagerDuty notifications and can deliver a more effective incident management response.
Check out the Pepperdata Integration Guide.
Interested in more? Be sure to check out all 150+ of our integrations.