PagerDuty Operations Cloud
PagerDutyExternal reviews
921 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Jeli does exactly what we want
What do you like best about the product?
We used to write prep docs for incident retro and analysis by hand - Google Docs, spreadsheets, that kind of thing. Having Jeli support building a timeline from data we already have in Slack is _magical_ for making that easier, and we've also used Jeli mid-incident: "hey, hasn't this happened before? How'd we fix it last time?"
The jeli slackbot for running an incident also helps us keep to consistent IR practices, which is extremely valuable as our organization scales. It's lightweight and non-prescriptive, but we can use it to remind people how we do things on our team.
The jeli slackbot for running an incident also helps us keep to consistent IR practices, which is extremely valuable as our organization scales. It's lightweight and non-prescriptive, but we can use it to remind people how we do things on our team.
What do you dislike about the product?
No notes, really. There's room to grow the featureset - integrating with more tools, ACLs to protect data relating to sensitive incidents - but we've found it useful as-is. Training people to use it took a little doing, but wasn't super hard; incident management is an expert practice, and it makes sense that even a tool that makes that practice more accessible is going to require some prep and user education.
What problems is the product solving and how is that benefiting you?
Makes it easy enough to analyze an incident that we do it more often - it used to require enough time and effort that we retro'd fewer of our incidents than we wanted. We've also used it to manage information streams for various audiences, particularly providing updates to non-eng stakeholders that appropriately summarize the ... chaos ... that often pops up in an active incident response.
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.
A fantastic tool for learning from incidents
What do you like best about the product?
The support offered by the Jeli staff is phenomenal. They helped us significantly improve the learning from incidents practice in my company. The Jeli tool allows our staff to analyse and share the incidents we have to increase our learning and drive incremental improvements.
What do you dislike about the product?
Learning a new tool is always going to be challenging and although the team have done a great job with lowering the difficulty of using the Jeli tool, there a minimum amount of time that will need to be spent on learning the tool. This investment of time is well worth it.
What problems is the product solving and how is that benefiting you?
Jeli allows us to ingest our incidents and analyse them with our collaborators. We also use the Jeli tool to present an overview of the incident during the incident review meeting so others can get insights into what happened.
Great tool for Incident and Problem Management
What do you like best about the product?
Jeli helped in streamlining the incident management process and improved the turnaround time to communicate and align resources during an incident. The flexibility and customization has helped my team to efficiently and effectively use Jeli (IR bot)
What do you dislike about the product?
There is a learning curve as it is with any tool, remembering all the commands associated with Jeli to effectively handle an incident that could be challenging in the initial phase.
What problems is the product solving and how is that benefiting you?
Since it integrates directly in slack, it enabled by team to carry out the lifecycle of the incident from an existing tool without having the need to login to a separate tool. The Jeli commands made it simple to provide incident details and global settings allowed to set update reminders and define default notification groups/channels.
Incident management... like a breeze now
What do you like best about the product?
User-friendly, adaptable and scalable. A great tool.
What do you dislike about the product?
Even though there are some restrictions regarding editing, Jeli team is always receptive to requests which could enhance their product to a new level.
What problems is the product solving and how is that benefiting you?
A great compiler which helps with time management.
Pretty good but needs better UI
What do you like best about the product?
It's straightforward and gets the job done. It also supports a good integration with all the tools and technologies that we utilize at the company.
What do you dislike about the product?
The UI seems dated. It doesn't look very clean or modern. I cannot think of any functionality that it lacks per say except for the UI.
What problems is the product solving and how is that benefiting you?
All our job failure alerts are hooked into PD and we use it to triage and mitigate these
Its a nice product
What do you like best about the product?
PagerDuty is mainly used for paging purposes, and we have various teams that work on call, so pager duty is very helpful and reliable when it comes to on-call rotation.
What do you dislike about the product?
Licensing costs are too high compared to ops-genie; if they bring down the price, that can be an excellent product for various companies. Other than that, I think all the features are user-friendly.
What problems is the product solving and how is that benefiting you?
PagerDuty handles our on-call alerting. This means when we have production-level outages or issues, they get sent to PagerDuty. PagerDuty has a schedule for our on-call support team and can send texts, emails, Slack notifications, and phone calls to the correct person to handle them. Within PagerDuty, we setup schedules so we know who is primary and who is secondary on-call so that way we always have coverage.
Jeli has made our incident management much easier
What do you like best about the product?
We were looking for an incident management tool that fit our existing processes. We looked at competitors other tools seem to have a pretty high entry configuration cost. Jeli was incredibly easy to setup. It helped us meet the requirements we had around communication, ease of use and fit our existing processes. In addition, their customer support team has been outstanding! They are always available to help us, providing training and updates on new features.
What do you dislike about the product?
So far the only downside has been that it takes a while to input information about specific opportunities. You'll get what you put into it but I wish it was a little more automated.
What problems is the product solving and how is that benefiting you?
Helps provide a consistent form of communicating about an incident. It creates our slack channels for each opportunity and provides a format to link documents and identify actors.
showing 131 - 140