OpsGenie vs. StatsD

Incident response is well suited to OpsGenie, and this is where it really shines—whether it's an outage, a security incident, or similar. My experience is mostly with security, and it offers a great audit trail. It minimises the need to cut and paste from different platforms when creating reports and ensures that what was said and what was done (along with any evidence) is persisted and reflected in the incident detail.

Incentivized

• Notifying through all the possible way like sms,mail and call.
• Ita shows the activity log it is usefull when your paging team through the incident through that you can check who has acknowledged or not.
• Notify the alerts to engineer as well as you can also add the description about alerts related what is it.
• Here you can schedule for on-call engineers

Incentivized

• OpsGenie New Jira design has made it difficult for those not familiar with that style.
• OpsGenie could benefit from nested escalation flows for team schedules. Creating a product alert that uses and Tech Schedule as well as an Incident Manager Schedule that already exists would create less overhead and ease management.

Incentivized

In general terms OpsGenie is a well done tool for solving the alert incident management, the usability is super ok during the configuration and during the alert. The main opportunity I found is the reporting and analytics section which is a little difficult to understand at a first sight and the refresh is not automatic, some little frictions but frictions at all

Incentivized

They are fully available at all times via chat, phone, or email and follow up thoroughly.

Incentivized

We also looked at PagerDuty but decided to go with OpsGenie as it had more features on the plan we needed compared to PagerDuty which would have required us to spend a lot more for what we felt were non-premium features. Everything felt like an add-on - automation for an additional $20 a user per month seemed like a lot on top of the base plan

Incentivized

• Helped us track bugs and issues that came up during product launch periods which reduced overhead that normally came with needing to manually contact the right team members
• Prevented last minute breaking issues from falling through the cracks, decreased time to fix by automatically alerting the team members and allowing the product and project teams to easily see what active alerts are in progress

Incentivized