PagerDuty Operations Cloud
PagerDutyExternal reviews
918 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Jeli is a great addition to the Incident Learning toolbox
What do you like best about the product?
Jeli is easy to understand for engineers new to incident reviews. It allows for those engineers to quickly come up to speed on how to create an informative and engaging narrative.
What do you dislike about the product?
There is little to dislike. As an early adopter we've seen quick development and rolling out of new features that address pain points.
What problems is the product solving and how is that benefiting you?
Jeli is being used to improve our quality and efficiency around Learning from Incidents. It allows our teams to have a consistent experience across reviews.
Pagerduty for alerting
What do you like best about the product?
It was best to use and user friendly and most useful
What do you dislike about the product?
Alerting frequently and some time unable to stop them
What problems is the product solving and how is that benefiting you?
Incidents and real time management
The only too l you cannot ignore
What do you like best about the product?
It does its job to notify you even when you usually would not have seen the matter. People can't ignore it; with that, it's easy to be sure that the team will be notified.
What do you dislike about the product?
Some integrations do not give enough details in the alerts, so we need to look for the info in each tool.
What problems is the product solving and how is that benefiting you?
Have shifts for alerting the correct person efficiently and managing escalations to the right level of support quickly.
Excellent tool to gather learnings from incidents
What do you like best about the product?
Jeli is highly focused on getting learnings ("opportunities") from incidents and making sure incidents are not wasted. Jeli is excellent for building a narrative around the events to gain the greatest insights.
Jeli offers excellent guidance and best practices on post-incident analysis. Jeli also focus on essential things such as being blame-aware and having a positive culture. Jeli will likely help us maintain best practices for incident analysis.
Jeli offers excellent guidance and best practices on post-incident analysis. Jeli also focus on essential things such as being blame-aware and having a positive culture. Jeli will likely help us maintain best practices for incident analysis.
What do you dislike about the product?
Some of the APIs are still in development. Look forward as more aspects of the API become available, for example, the ability to extract data tagged data from incidents via API.
What problems is the product solving and how is that benefiting you?
Finding the best learnings from incidents. Tagging data with custom data.
Pagerduty for efficient on-call
What do you like best about the product?
Integration with multiple open source and proprietary monitoring softwares
Easy to define schedules that works well even for a big team which sits across the globe
Developer friendly and great ease of use and UI/UX
escaltion polices can be defined at multiple levels with different thresholds
Easy to define schedules that works well even for a big team which sits across the globe
Developer friendly and great ease of use and UI/UX
escaltion polices can be defined at multiple levels with different thresholds
What do you dislike about the product?
some intergration with open source monitoring tools are not as good as with proprietary softwares, they should cover them as well as not every company is using paid or popular open source softwares, some are using the new starups softwares for monitoring.
What problems is the product solving and how is that benefiting you?
Alerting the users for different types of incidents and streamlining the on-call process for companies.
Jeli is the future of Incident Analysis.
What do you like best about the product?
Jeli's solution focuses on the human element. So many other solutions in this space focus on root cause analysis and other technical automations that fail to recognize that the necessary ingredient for a resilient system is people. Root cause analysis is at best a waste of time, because it enables hindsight bias to place blame on a technical accident. You can't prevent accidents. Focusing on the 'cause' of an accident is a waste of time, because you can't do anything about that. Instead using Jeli you can learn from the narratives of the people closest to the work, and you can use that to identify and fill in knowledge gaps distributed throughout the team. That is useful!
What do you dislike about the product?
It isn't obvious how to get everyone to buy into the concept of using Jeli at first. If upper management isn't on board yet, then you need resources outside of Jeli to convince them of the approach.
What problems is the product solving and how is that benefiting you?
Learning from incidents (LFI) so we can make our software more robust.
Amazing Product
What do you like best about the product?
Jeli is an absolutely amazing product. It is so simple to use. The tagging features are amazing. Using the product has saved us so much time compared to doing manual Incident Analysis. I highly recommend Jeli.
What do you dislike about the product?
Nothing, it is intuitive, easy to use and has a great team supporting it.
What problems is the product solving and how is that benefiting you?
Jeli makes it easy to learn from incidents. We can use the tool to analyse an incident and tag certain properties to it. It is saving us a lot of time and effort.
Useful incident management tooling... for the first time?
What do you like best about the product?
Jeli is easy to use and makes organizing, analyzing, and, more importantly, *learning* from incidents much easier.
What do you dislike about the product?
I have no complaints. A more advanced import from Slack would be helpful for incidents that arise in the middle of everyday business.
What problems is the product solving and how is that benefiting you?
Jeli makes it way easier to rally the team around an active incident, clarify roles, keep people informed, and, most importantly, learn from our incidents over time. This has made our organization and platform more resilient overall.
Fundamentally changed how I view incidents
What do you like best about the product?
Fundamentally changed how I view incidents as opportunities to learn, helps my investigation be focused and efficient, and increases the learning for myself and the org.
What do you dislike about the product?
Do I need to fill this out? There isn't much. Jeli is in the early stages its journey and my only "need" is more from the great team and can't wait to see what they build next.
What problems is the product solving and how is that benefiting you?
Jeli helps me gain a deep understanding of what happened leading up to and during an incident both with our human and technical systems.
Jeli helps me find and share the stories of incidents
What do you like best about the product?
At the start of an incident, Jeli collects the slack-based evidence of the incident, without my staff having to fill in timelines or details.
After that, I use the Narrative Builder to pull the important moments out of what happened and what we did, and build a narrative supported by those events.
During the incident review itself, that supported narrative guides the review group through what happened, and I feel that we very readily get at our expectations, assumptions, and learnings.
After that, I use the Narrative Builder to pull the important moments out of what happened and what we did, and build a narrative supported by those events.
During the incident review itself, that supported narrative guides the review group through what happened, and I feel that we very readily get at our expectations, assumptions, and learnings.
What do you dislike about the product?
I have not been unhappy with Jeli the product or Jeli the company.
What problems is the product solving and how is that benefiting you?
We as an organization appear to be able to have high-quality discussion and learnings from the incidents we have, while spending less time preparing for those discussions.
showing 51 - 60