External reviews
External reviews are not included in the AWS star rating for the product.
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.
- Leave a Comment |
- Mark review as helpful
Pager duty review
What do you like best about the product?
Pager duty is one of the best in industry for alert management
What do you dislike about the product?
Its voice prompts in calls is very pitchy it should be improved
What problems is the product solving and how is that benefiting you?
Alerting management is one the critical componentss ion production statbility. Its helped us in preventing a lot incidents.
24 * 7 Monitoring tool
What do you like best about the product?
Its way of sending alerts is from various methods like calls, mail and messages, ensuring alerts aren't missed. Its way of alert incident management is one of the best.
What do you dislike about the product?
Not so much customisable interaction with JIRA. You have to keep an alert id to get alert history.
What problems is the product solving and how is that benefiting you?
To auto-assign the alerts to the respective on-call person. Manage any incident timely, which helps system availability.
Great tool that helps our org learn from incidents
What do you like best about the product?
Support is amazing. Jeli is constantly iterating and improving. I love the timeline tool that makes the incident review process more manageable.
What do you dislike about the product?
Haven't found any yet, I think I need to use the tool more to better understand it and see if there are any needs it doesn't currently meet.
What problems is the product solving and how is that benefiting you?
Incident timeline management and searching for similar incidents
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.
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.
showing 81 - 90