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. 

We are using the cloud version of Atlassian products now, but I think the Data Center version we used earlier was much more user-friendly. There are lots of limitations in the cloud version The add-on or features that work with the Data Center versions are not compatible with the cloud version.

Opsgenie fits on top of the base application, which is Jira Service Management. Jira Service Management is an investigation. Previously, we had Jira Service Management and PagerDuty running on top of that. Now, Opsgenie is bundled as a part of JSM. However, when we switched to the cloud version, many of the features have become a bit complicated compared to the Data Center version I had used for years. It might be due to an architectural change or some other reason:

Also, it would be nice if Opsgenie had the ability to import rosters from other sources like you can do in PagerDuty. 

I have only been using Opsgenie for two months. 

Opsgenie is reasonable. 

The cloud version is scalable and it can fit everything from small organizations to large enterprises. A small or medium-sized enterprise could afford it. 

I rate Atlassian technical support 10 out of 10. Their support is excellent. They don't have local support in India. They schedule a meeting with us the moment we raise a ticket. There usually aren't any problems with the time difference because Atlassian support is based in the UK. 

Positive

We previously used PagerDuty. There isn't much difference in the basic functionality. I would recommend either depending on the kind of tools you are using. If you are using Atlassian products, Opsgenie is the best choice because the features are the same and it is bundled with Jira Service Management. If you are using something than Jira, it depends on the size. PagerDuty is more appropriate for larger deployments. 

I rate Opsgenie nine out of 10 for ease of setup. 

I rate Opsgenie eight out of 10 for affordability. Opsgenie is on the cheaper side, and it fits our budget. I estimate the license costs around $400 to 500 annually for 15 users. The price is available on the internet. It's a standard, straightforward price.

It's bundled into Jira Service Management. After we purchased JSM, we no longer needed to pay for Opsgenie. 

We use OpsGenie for alert management and incident management. We have integrated it with three different tools. We have integrated it with Nagios, SolarWinds, and AppDynamics. These three tools generate the alerts that are sent to OpsGenie. A regular alert moves as a Jira ticket. So, SolarWinds is the source, OpsGenie is the mediator, and Jira is the end receiver. People interact more with Jira. It is a part of our alert management.

For incident management, we have given access to a few of the service desk engineers. They're using OpsGenie for incident triage and documentation. Incident management, triage, and chronology are captured in Confluence. We have an option to export to Confluence. So, we are able to capture various types of information such as what happened, who gave an update, when the incident got closed, and how they got the solution. The root cause analysis process is being managed by OpsGenie.

It is completely on the cloud.

I am a Jira admin. The best feature for me is that I do not need to write different code when I integrate with multiple applications. OpsGenie made it easier for me. All I need to do is create a field and give a value. I need to set the parameters and give a value. I can write only one script so that it directly interacts with my Jira and feeds all the data. 

We went with OpsGenie because it was simpler to integrate with Atlassian products. We are able to use the OpsGenie connector to connect with our Jira servers. It is easy, and the latency is good. Even though our Jira is on-premise and OpsGenie is on the cloud, it is able to cope.

It is also easy to use. A newbie is also able to easily understand and use it.

It doesn't have a proper way to convert the alerts into incidents. Every alert isn't an incident. A few will have less priority, and a few will be incidents.

The handshake with the monitoring tools can also be improved. When there were a bunch of alerts or the number of alerts was more than a thousand in a minute, OpsGenie wasn't able to handle everything properly. The handshake issues were there.

The ease of access could also be better. It is a little difficult for us to integrate it with our existing SSO. For the configuration, every time, I have to reach out to Atlassian. If they can blend it easily, that would help.

It would help if there is a feature to create an alert from Confluence based on any existing one.

Their documentation can also be improved. Their knowledge base is not sufficient.

It has been about one year and nine months.

The product is okay. We had noticed that when a server or cluster goes down, there were a few alerts that got missed. We already reported it to the vendor, and they said that they are working on it and it might get fixed in the next version. Since then, we haven't observed the issue. 

It is completely on the cloud. So, it should be scalable, but I am not sure. 

We have acquired 100 licenses of OpsGenie, and we have about 65 concurrent users. Most of them have different kinds of roles, but the number of concurrent sessions would be at a max of 65.

I have worked with them on several use cases. Their documentation isn't good. So, whenever I had to do any new or additional integration, I used to reach out to them, and they used to help me with the issues I was facing. I also interacted with them about the handshake issue.

I would rate them a 4 out of 5 because they're good. They provided me with a sandbox whenever I needed something for testing. They were able to help me out when I had issues with integration.

Positive

It isn't that difficult to set up. It is easy, but its documentation can be improved. The tool implementation is good, but the documentation is not sufficient. I got to know by exploring myself but not everybody gets that much time.

The deployment, including testing and everything else, took us one and a half months, which is good because we had enough time on our hands. We migrated from ServiceNow to Jira and then went for Opsgenie.

We have opted for a yearly subscription. The initial quote given was about $29, but I don't know the actual price. There might be some negotiations during renewal.

You have to choose a product based on your environment. OpsGenie is most suitable when you have a sibling product. If your company has Atlassian products, OpsGenie is the best choice. It also works if you are using ServiceNow. 

I would rate it a seven out of ten because there are lots of improvements to be done. 

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.

There is always room for improvement with any tool. They could introduce many more features, which we believe is on their roadmap. If we want specific features, we have to create tickets for Atlassian, and their people can oath. If they get a suitable oath on a specific feature, they will implement it.

We have been using this solution since 2021. Opsgenie was an independent product-based organization but was later acquired by Atlassian in 2020. There are no versions with Opsgenie, and it's a SaaS-based product.

It's a cloud-based product, so we do not update it manually. For example, we can complete updates on Android or Apple phones when we want. But in the cloud version of Atlassian tools like Jira or Opsgenie, they do not send us prompts and update it in the background.

It is a stable solution, and the performance is good.

It is a scalable solution. Atlassian tools used to be restricted to 5,000 users but are now open to any number of users. We need two employees to configure and integrate the solution.

It is a per-user license, and you can create your team and another team. It can be five or ten members, but it's up to them how many systems are integrated with Opsgenie.

I don't believe we have used technical support, but Atlassian support is available for Opsgenie if needed, and I know they are good. There are different response times based on the different types of plans, like basic, advanced, and premium plans. So response will be dependent on the plan.

For technical people, the implementation is easy and not complex. But for non-technical people, implementing it will be a little bit difficult.

We do not have to install it because it's a cloud-based product. We just create an account, and it is good to go within five to 15 minutes. Then we have to configure it. No third party is required, and you can configure it very easily.

There are monthly, and yearly subscriptions with Opsgenie and the per-user license depends on the plan. It varies from about $5 to $15 per month. There are different basic, advanced and premium options, and the licensing costs depend on the plan. For example, in an enterprise plan, there are full feature options, and it costs approximately $30 per user. The standard costs $19 per user, and the basic costs about $9 per user, per month.

I rate this solution an eight out of ten. We work in a service-based organization, and clients come to us for support on Opsgenie. So our role is to configure it for them, but it is their decision on how they want to use and handle it. They also decide how many licenses they want to use.

Regarding advice, it is a good tool, and the integration is seamless. Most companies are using Atlassian tools and can get better integration and support. You can pay for licenses and do not have to deal with different vendors. Under one umbrella, you can access development and incident management tools, like Jira, Confluence, Opsgenie, or any other development-related tool.

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.

Neutral

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.

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.