You asked and we’re delivering! We’re introducing several new and exciting features to PagerDuty’s ServiceNow integration that you, our customers, have requested. Our most anticipated new feature utilizes ServiceNow CMDB (Configuration Management Database) data to easily build service hierarchies in PagerDuty through business service dependencies.
At this year’s SaaStr Summit: Enterprise, our CEO Jennifer Tejada talked about why digital acceleration has been one of the positives to come out of the COVID-19 crisis, and why this time for change shouldn’t be wasted. Here are three key takeaways that she shared. The crisis, as Jenn explained, is accelerating permanent change in the role of the CEO.
Many organizations are looking to implement DevOps due to the promise of increased release velocity, better developmental agility, and the ability to free up time for developers to focus on innovation. However, adopting DevOps isn’t a panacea— instead, the idea of communication, collaboration, and blameless retrospectives that a DevOps model encourages can help foster a leaner system where bottlenecks are solved in a manner that not only fixes the problem, but also improves the process.
Anyone who’s ever played the game of chess knows there’s more than one way to reach a desired outcome. There are 400 possible setups after the first turn; 197,742 after the second; and just north of 120 million after the third—all of which are marching toward the same desired outcome. “So, what does any of this have to do with DevOps?” you ask? Fair question.
Agile is a popular buzzword in software development, with some organizations and teams masquerading as “agile” while they are actually doing something very different. I’ve seen it numerous times in my career as an Agile Coach: A leader claims to embrace agile values, but micromanages engineering teams and uses agility as a way to manipulate developers to work long hours. The result?
Earlier this month, many areas of the internet experienced a major incident caused by a router misconfiguration within a highly used service provider. This led to cascading service failures, causing widespread outages and disruptions for several well-known SaaS organizations. When the outage occurred, our teams at PagerDuty immediately noticed a global spike in events and incidents.
We’re excited to announce a new set of product updates and enhancements to the PagerDuty platform! PagerDuty partners with organizations to help teams create efficiencies across IT organizations and protect customer relationships. These updates will help further improve your team’s ability to manage and reduce noise, automate critical response workflows, and quickly mobilize a response in order to mitigate disruptions across your digital operations when seconds matter.
Solving incidents is hard. Depending on your current situation, you may also be losing a lot of time figuring out what notifications constitute an incident. This results in more and more lost time as every notification must be triaged as a potential incident before you can proceed to move to resolve or disregard (as a non-incident). All this may sound very cumbersome, but the fastest way to improve is to learn and define what incidents are. And you’re in luck!
In June, we were delighted to host our first ever virtual PagerDuty Summit EMEA! Llywelyn Griffith-Swain, SRE Manager, and David Jambor, Head of Systems Engineering at Vodafone, were among our speakers. They outlined Vodafone’s approach to achieving immutable telemetry. David opened the session by defining Vodafone’s strategic goals. “Our vision is to create an engineering-driven culture,” he explained. “We want to empower development teams to be self-sufficient.
Your payment systems have slowed to a crawl, customers are getting impatient and abandoning their shopping carts both online and in stores, and you’re losing money every minute this problem goes on. Behind the scenes, technical responders are scrambling to resolve the issue before it impacts more customers—and before even more money is lost.
