PagerDuty Operations Cloud
PagerDutyExternal reviews
918 reviews
from
and
External reviews are not included in the AWS star rating for the product.
It's hard to imagine a better incident management tool
What do you like best about the product?
Jeli provides the structures and reminders the team needs without getting in the way. It's got a low barrier to creating incidents, automated workflows are incredibly optional, and the incident reports at the end are informative and readable. We use it for every incident and the incident overviews are great at giving Customer Support the right amount of information.
What do you dislike about the product?
It can take a long time to really put together a good timeline and determine which messages are the most critical.
What problems is the product solving and how is that benefiting you?
Jeli provides a light weight way to structure incidents. Easy to forget pieces of process like updating the incident status can be automated through reminders for example. We bought it for incident reporting, but we use it for every incident because it makes the actual incident process so much smoother.
Amazing product, awesome team
What do you like best about the product?
Great insights into our incidents. Helps our incident responders write awesome incident reviews that make it easy for others to learn from. Beyond a really great product, the team truly treats us like partners, and have gone out of their way to help us level up our incident response and review process.
What do you dislike about the product?
I haven't seen any so far, it's been a huge help and the people we work with are incredible resources.
What problems is the product solving and how is that benefiting you?
Incident review, along with all of the learning that is necessary to make incidents have value for our teams and our customers.
Incident Analyst's most trusted tool
What do you like best about the product?
I like the flexibility of Jeli. It acts as a Swiss army knife for incident analysis and can support a wide array of uses to learn more from incidents.
I use it every day and it has made analysing incidents so much easier (and fun) compared to doing it manually.
Being able to pull in multiple incident Slack channels and individual messages allows me to tell more interesting and complex incident narratives. The end results with the visual narrative look better too.
Creating the narratives takes effort but it forces the investigators to pause and look closely at what happened. Investigators pick up on a lot more threads to pull on in the investigation and for the Post Incident Review meeting which leads to better insights and more engaging PIRs.
I use it every day and it has made analysing incidents so much easier (and fun) compared to doing it manually.
Being able to pull in multiple incident Slack channels and individual messages allows me to tell more interesting and complex incident narratives. The end results with the visual narrative look better too.
Creating the narratives takes effort but it forces the investigators to pause and look closely at what happened. Investigators pick up on a lot more threads to pull on in the investigation and for the Post Incident Review meeting which leads to better insights and more engaging PIRs.
What do you dislike about the product?
Could support conversations between incident analysts and readers of the report better
What problems is the product solving and how is that benefiting you?
We use Jeli for Incident Analysis (after incident is resolved).
Different roles use the tool to a different extent.
a) In my department at the higher level we use Jeli to gain an overview across incidents and make use of the exec summaries.
b) At a group level we also use Incident Narratives and Takeaways that allow non-responders to understand what happened and what we learned. It also allows us to see patterns.
c) Individual Incident Investigators, often Team Leads/Lead Engineers/Principal Engineers or Senior Engineers, create Incident Narratives to build a better understanding of what happened even for incidents where we don't run a PIR.
d) Investigators use Jeli during the PIR meetings to summarise the incident via the visual narrative timeline and capture insights from the PIR meeting in the takeaway section afterwards
e) We also sometimes use Jeli as a training/education tool in that we analyse the coordination and communication aspects of past incident response and use that to teach other incident responders.
Different roles use the tool to a different extent.
a) In my department at the higher level we use Jeli to gain an overview across incidents and make use of the exec summaries.
b) At a group level we also use Incident Narratives and Takeaways that allow non-responders to understand what happened and what we learned. It also allows us to see patterns.
c) Individual Incident Investigators, often Team Leads/Lead Engineers/Principal Engineers or Senior Engineers, create Incident Narratives to build a better understanding of what happened even for incidents where we don't run a PIR.
d) Investigators use Jeli during the PIR meetings to summarise the incident via the visual narrative timeline and capture insights from the PIR meeting in the takeaway section afterwards
e) We also sometimes use Jeli as a training/education tool in that we analyse the coordination and communication aspects of past incident response and use that to teach other incident responders.
Easy to use!
What do you like best about the product?
The UI is very intuitive and sleek. We love using Jeli for incident reviews! Being able to export incident messages straight from Slack into Jeli to create a timeline is very useful.
What do you dislike about the product?
There are a few features that would make Jeli even better, just as having the ability to collaborate on the meeting notes together. Otherwise, I don't dislike Jeli at all.
What problems is the product solving and how is that benefiting you?
Jeli is making it easier for us to conduct incident reviews and facilitate learnings/healthy discussions around incidents.
Great and effective platform for incident management
What do you like best about the product?
The platform has everything you need for using as a tool to learn from incident. It has all the cool features that you can use for PIR meetings, and also the team is great at getting feedback to improve their tools and fix any issues that may arise.
What do you dislike about the product?
Maybe the learning curve is not really low, so you still need to learn it a bit, but then after 1 or 2 times using it, it will be super easy.
What problems is the product solving and how is that benefiting you?
It helps to provide the tool to be easy to learn from incident, by exploring different angles of the incidents.
Allows us to spend more time on learning from incidents!
What do you like best about the product?
For us, Jeli has been great for eliminating the burden of managing the administrative side of incidents. As an enterprise company, we work hard to monitor the impact that incidents have on our business, and that comes with some administrative tasks to ensure we capture the right information. Jeli has allowed us to automate many of our processes and enable our engineers to declare and go.
Aside from the IR bot, the actual narrative builder has been a huge time saver with auto import of the information we need whereas we had to scrub slack for all related events and messages and run our retros from a Google Doc. For incident management, the most important part of it all is recovery and learning about happened, by removing the overhead of data collection, we're able to jump right in with no hesitation and are retro-ing more often because the burden of preparing the necessary information is taken care of for us.
The Jeli team as a whole has been incredible! They're exceptionally responsive, friendly, and care deeply about their customers. They've gone as far as building out custom functionality to support us and listen to their customers need. Special shout out to Lesleanne who has been our primary contact and an absolute joy to work with. I'm excited to see what Jeli comes up with in the future, as from what I've seen, the roadmap looks very promising.
Aside from the IR bot, the actual narrative builder has been a huge time saver with auto import of the information we need whereas we had to scrub slack for all related events and messages and run our retros from a Google Doc. For incident management, the most important part of it all is recovery and learning about happened, by removing the overhead of data collection, we're able to jump right in with no hesitation and are retro-ing more often because the burden of preparing the necessary information is taken care of for us.
The Jeli team as a whole has been incredible! They're exceptionally responsive, friendly, and care deeply about their customers. They've gone as far as building out custom functionality to support us and listen to their customers need. Special shout out to Lesleanne who has been our primary contact and an absolute joy to work with. I'm excited to see what Jeli comes up with in the future, as from what I've seen, the roadmap looks very promising.
What do you dislike about the product?
Thus far, nothing that we've disliked! We've requested a few customization options which are on Jeli's roadmap and they've been great in working with us and their other customers to influence prioritization of their features. One thing that I do love about Jeli is the simplicity, whereas other incident management platforms feel bloated or like they're trying to do too much.
What problems is the product solving and how is that benefiting you?
Reducing the burden of administrative tasks which allows our teams to better focus on learning.
Best alerting application
What do you like best about the product?
Pagerduty provides the best UI to manage teams , services and their schedule. You can create different types of alerts depending on the severity of the issue. You can integrate it with the different apps like teams , Gmail, slack to get notified.
What do you dislike about the product?
Multiple alerts at the same time can be confusing. So inorder to check the multiple things at a time you need to set a schedule. So due to this issue , the acknowledgement to the incident sometimes get difficult and need to login to the system to ack/ resolve.
What problems is the product solving and how is that benefiting you?
Two major problems incident management and alerting is resolved with the Pagerduty. You can create teams , manage their services and create schedule and so easy overrides. So many things under one place.
Thoughtful, thorough, friendly, clear, and concise!
What do you like best about the product?
Jeli gets people excited about learning from incidents. It's thoughtfully designed to maximize the limited time most orgs are willing to spend on post-incident work, and the incident response features match my team's needs. Our rep Chloe is amazing and extremely helpful - providing training, gathering feedback, and all this made our launch very smooth. Jeli is easy to set up and configure on your own, but the support from Chloe and the team were above and beyond. I also really appreciated the data/metrics-driven approach and goals when we launched.
What do you dislike about the product?
Learning from incidents isn't the same as the root cause analysis process that most people are familiar with. Jeli definitely makes the learning approach much simpler, but I think they rely heavily on an internal sponsor to help show the true value. Your org might need to be "ready" for Jeli and the learning from incidents approach, although they make this so easy from the start.
What problems is the product solving and how is that benefiting you?
Getting the most learning and value from incidents (opportunities!) in the limited amount of time we're willing to spend on post-incident work. Additionally, helping us clearly and easily coordinate during incidents.
An incident management platform that does it all..
What do you like best about the product?
Jeli allows me to deeply analyze every incident without spending a lot of time on it. I gain time back, can prioritize other projects without compromising on quality. It allows all stakeholders to get what they need and without being in tech, Jeli, is broadly applicable to my industry.
What do you dislike about the product?
We haven't run into any major downsides so far. The team and the product are very helpful. We're looking forward to what they come out with next.
What problems is the product solving and how is that benefiting you?
Jeli is allowing me to perform a diligent incident management process, keep people aligned in my org. And allows me to resolve my incidents so I can maintain customer trust.
"A pleasure to work with"
What do you like best about the product?
We decided to use the Jeli incident bot to replace our homegrown tools for incident response and engaged in a trial of the full product as part of that -- we were honestly kind of bowled over by how everyone at Jeli was very engaged with us on switching to using the bot and eager to take feedback. We got great advice that really helped us smooth the transition, and almost everyone who has touched the Jeli tools has talked about how much easier things are with them and how they've really helped smooth out communications and data gathering.
What do you dislike about the product?
I honestly can't think of anything right at the moment -- the biggest issue for us is the cost of the full product for an organization of our size right at the moment, especially when it can be hard to articulate the benefit in the short term.
What problems is the product solving and how is that benefiting you?
Our previous incident managment process used a bunch of hacked-together Slack workflows that had a lot of friction when it came to opening incidents, keeping the rest of the organization updated, and taking notes for future use. This led to a lot of stress around incidents, especially for coordinators, and added an implicit level of resistance to even opening incidents. Using Jeli has made this entire process pretty seamless -- incidents are easy to start, it's easy to add updates to incidents (without cluttering Slack channels!) and now that we automatically open separate channels for every incident, it's easy to have one place to collect the communications around an incident. It's also making it easier for people to see the benefit of doing our communication in Slack rather than a voice or video call, where we tended to lose a lot of context before.
showing 41 - 50