Opsgenie Reviews

We use Opsgenie to create alerts from Grafana and we print those alerts with a format of cases on the Opsgenie console and as well as those interconnected to teams. We have more than 200 people using this solution. 

In a future release, we would like to receive alerts when a specific threshold is reached and to escalate the reason for that alert. 

I have been using this solution for a couple of years. 

This is a stable solution. I would rate it a nine out of ten for stability. 

This is a scalable solution. I would rate it a nine out of ten for scalability. 

 I would rate the technical support for solution a seven out of 10.

The initial setup is straightforward. I would rate the simplicity of the setup an eight out of ten.

There is not much difference between PagerDuty and Opsgenie. Both are easy to use and convenient from a integrations, automations, APA connectivity and GDA perspective. We chose Opsgenie based on cost and our requirements. 

Whenever Opsgenie involves automations and there is a big number of teams or  applications to handle, a good integration with APA services is required. 

Opsgenie as a product is good. I would rate it a seven out of 10.

The primary use case of the solution is to schedule on-call personnel and notify them about any alerts that require their attention.

The most valuable feature is the ability to automatically create a ticket for the support team when there is an alert.

The solution has room for improvement by providing bundle pricing with other products that are frequently used together from Atlassian.

I have been using the solution for two years.

The solution is stable.

I previously used PagerDuty and am in the process of switching over because this solution is more user-friendly and works with the other tools I am using.

The initial setup is straightforward.

The implementation was done in-house.

The cost of the solution depends on the package you select and is per user.

Before making my selection I also evaluated PagerDuty.

I rate the solution eight out of ten.

This solution has a number of great features that organizations may find helpful. I recommend the solution to anyone. 

Monitoring and interim management are the two main features for which we are using OpsGenie. 

We have an infrastructure with around 400 plus critical nodes that we are monitoring. They are scattered across various geographies and include on-premise switches, servers, other devices, and a few cloud services. There are 10 to 20 engineers who monitor it.

We also do total remediation of our own. If something is broken, we'll try to fix it through our software. 

The use cases also vary depending upon the client's requirements while designing a solution. We are a kind of service provider. We have our own in-house cloud management software. Based on a client's needs, we evaluate and provide the inputs. 

One of the reasons for implementing OpsGenie was to have a completely automated system where there is no need to monitor and call someone if something breaks down. Previously, manual intervention was required. If something went down, it had to be followed up with people and escalated. Now, it is a completely automated system. There is very little manual intervention.

Another reason for implementing OpsGenie was the integration of different alerts in one single console.

The integration feature is the most valuable. It provides a lot of customizations for the integrations we use. 

OpsGenie needs to keep up with its competitors in terms of new features and pricing.

We have been using OpsGenie for almost two to three years.

It is very stable. We feel very good about this. We haven't had any issues or problems with production or operations.

We don't scale up at this moment. 

Sometimes there was a delay from their side in providing a solution, and we didn't like it. I would rate them a seven out of ten in terms of support.

We had completely person-driven or manual management. We had other open-source tools as well for monitoring, but now, we have integrated everything into OpsGenie.

The initial setup was very straightforward. It is like plug and play. It took three to four hours to go live.

We took care of the implementation on our own. In terms of the implementation strategy, we first tested and evaluated it with our lower environment and then re-upgraded directly to the broad environment. It was very straightforward. We didn't have to plan something very complex.

We have seen a return on our investment with OpsGenie. Compared to things like reporting where we used to spend a lot of money, the cost reduction is 20% plus.

Now, we are one centralized team in one place. We don't have a service management team all across the bases, and there's a reduction in headcount as well. We have been able to reduce almost six full-time employees. 

From the pricing perspective, they are on the higher side as compared to other competitors.

We did not really evaluate. OpsGenie was endorsed by one of our other companies and that's why we went with it. We were already using a couple of Atlassian products like JIRA, JIRA Help Desk. The integration with these products is very seamless. That's why we went for OpsGenie.

It's a good product. We never faced any issues in managing this. You can definitely go for OpsGenie if it suits your environment. It's not only about the features and money. You should also feel comfortable with the product.

I would rate this solution an eight out of ten. Every product can have some improvements. We have been using it for almost two to three years in this company. There might be some new features, or other products, like PagerDuty, might have already improved over OpsGenie in terms of the features.

We have a monitoring tool called Nagios, and we integrate Nagios and OpsGenie. The tickets flow from Nagios to OpsGenie. 

We have automation scripts. OpsGenie has the capability to resolve the tickets if it is predefined. If an instance goes down, then to restart the instance, we have inbuilt scripts. When the ticket comes, like instance down or instance failed, we will configure it back to restart the instance. So, that will happen with OpsGenie. It's an incident management tool.

OpsGenie has many features, such as email notification, SMS notification, roster, tracking of the tickets. Automation, like scripting, is also possible.

There are also features for maintaining the history of the tickets and all the solutions related to how it was resolved previously. If there are similar kinds of tickets, we can look at how a person is working on that ticket. If he doesn't have any idea, you can look back at a similar ticket and solve it as the previous person did it. 

It should have a lot of plugins. It should also come with cloud integrations, which are not that great with OpsGenie as of now. It should have AWS, Azure, and Google cloud integrations. 

It should also provide automation, that is, it should open somewhere, like orchestration. Something like the orchestration that ServiceNow is doing. That would be great. Orchestration is the main thing. If OpsGenie comes with stack down feature, not completely but some part of it, and orchestration is there, that would be beneficial.

I have been using this solution for the last one year. 

It's a scalable solution.

We bought it from a third-party. They're really good, and they're helping. We didn't face that many issues.

The initial setup was very straightforward. The deployment part took one to two weeks. 

Initially, OpsGenie was new to us, so to understand its features, we had a lot of difficulties, mostly on the automation side, such as how to redirect tickets, etc.

I recommend OpsGenie because if you compare with DataDB, the cost is very nominal, like $10 per user. It has almost all the features that DataDB has. It is a good automation tool. It's not only for incident management. You can also use it as an automation tool. It has a good automation environment.

I would rate OpsGenie a seven out of ten. It is a good product, but it needs a few more features.