Opsgenie Reviews

We use Opsgenie for the same purpose as PagerDuty. It is a tool that provides incident alerts to our application and production support engineers. We started with a team of 12, but we plan to expand to around 50 people by next year. 

Opsgenie is easy to configure and use. 

I've integrated it into a tech demo. It's basically in our system, a system tool. I've done some deduplication inside of it. I can also set the force by directional communication from JSM. 

Opsgenie is really good. It integrates pictures and links directly into Jira Service Management. And that enables it, it enables vision and between getting the problem solved and finding who to find to solve that problem. So, Opsgenie is a really good tool.

We used it for incident reports. It often involves creating custom Jira Query Language (JQL) to pull data on assignees, whether looking at individual members, teams, groups, or overall service products and then generating reports. 

You can examine SLA breaches, response metrics, and workload distribution across the service desk. While Opsgenie itself may not be necessary for pulling such statistics, it significantly enhances clarity within the organization.

That clarity, visibility, scheduling, and the management of on-call schedules, as well as tracking SLA breaches and workload, are key reasons to utilize Opsgenie.

The SMS feature, which costs money to send texts unless you have the higher version where it's included for free, is particularly useful. For instance, during migrations or downtime events, especially if they occur over a weekend and the involved personnel aren't present on Monday but there's a critical issue, this feature allows for immediate contact via text. 

Given that most people tend to mute email notifications but remain active on their phones, the SMS feature is invaluable for urgent communications, ensuring the right people are alerted in emergencies. So, these are the alerting features in Opsgenie I've found most effective.

We use this solution for incident management. If we host a website or run a server, we can get a notification or alert if our system is running. When we integrate it with other web monitoring tools and there is a glitch or function, it automatically creates a ticket or alert. For example, we get a call, a message, or an email, and if we integrate it with the Jira Service Desk, it automatically creates a Jira Service Desk ticket and assigns it to the support team member.

Opsgenie integrates with Atlassian and other web monitoring and incident management tools. I used to work with other Atlassian tools, like Jira and Confluence, and whenever we look for any tool, we prefer to go for a one-family solution because it makes the integration easy. We also compared it with other tools, and Opsgenie worked much better.

We used Opsgenie to monitor all our infrastructure environments, on-premises such as offices, data centers, etc., but we also had a huge cloud environment in AWS or Amazon, so those environments were also monitored with Opsgenie. It's a very useful and important tool.

During my work period, Opsgenie had alerted us several times about excessive heat in the data centers/communication rooms when the AC went down, so it practically "saved" our network equipment, servers & UPS devices from becoming faulty, due to overheating. It also helped to detect network outages. 

Opsgenie primarily functions as an on-call management tool. It integrates well with Jira Service Management (JSM) and other Atlassian products. It offers a robust solution for managing alerts and incidents within Atlassian's ecosystem rather than relying on separate systems for phone call details.

We integrate Opsgenie with our monitoring tools or IT incident alerting systems. Integration with most tools is straightforward, often as simple as adding an API key or URL. For tools without direct integration, we can customize using Opsgenie's API to ensure seamless connectivity.

Moreover, we have different alerting channels. Escalation policies in Opsgenie have enhanced our response time by diversifying alert methods beyond email to include calls, SMS, and other integrations like WhatsApp through public APIs. This multi-channel approach ensures that alerts are noticed and acted upon quickly.

We have several different teams that need to be on-call for several different products. So, we use Opsgenie to manage that, and we also use it for routing our alerts from a different monitoring service. 

We also use Opsgenie to control some of our schedules for different activities. For example, we have internal support for some of our teams, and even though this does not require the teams to receive any types of alerts or monitoring, we still use it for scheduling so that it can control who will be the next on-call person.

We are using it as a service. So, we don't host it in any way. I believe we are using the latest version because we do not control its version. It's a service.

We can rely on the product to organize our schedules. We don't have to think about who will be next on-call. The system already gives us the answer. We don't have to waste time organizing how people are going to be covering each of their rotations. There's also an override option. So, it's easy to reschedule or reorganize our schedules when someone goes on vacation or when someone is on sick leave.

It's also easy for us to understand whom to contact when we have an issue. So, if we receive an alert, we have the first person on-call, but we can also organize different people to receive these alerts depending on our rules. 

We use the product for email notifications from the automatic application.

Opsgenie has streamlined our communications and alerting.

We have CloudWatch metrics like Grafana and AWS metrics that tell us about our registration counts, the services we run, such as microservices running on containers, and container orchestration systems like Kubernetes. 

We need to know how many resources are being used, how many services are being utilized, and how many registrations are expected and how/are not expected.

We are establishing thresholds. Opsgenie receives all of those alerts and simply notifies us if there is a P1 issue, (a priority one issue) for us. 

My company is a financial services company. Priority one issues are more likely to be related to services that have an SLA of 99.9999% and the service is down for example. Opsgenie sends alarm alerts to the appropriate people at the appropriate time. 

We have schedules, and we have on-call personnel who will receive Opsgenie alerts in the form of a call or a message.

The schedule varies according to the individual. Then he'll get a call from the next guy on his calendar. Opsgenie manages everything.

The product is integrated into almost all services, including Grafana, AWS, and others. 

The Opsgenie integration, which is based on a webhook or something from a third-party tool, is something that is appreciated. We can integrate Opsgenie with any third-party application.

Integration with other solutions is one of the most valuable features of Opsgenie.