Opsgenie Reviews

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.

My opinion is more relevant when we have an auto-generated call. Typically, the alerts are vague at times. However, when the automated callers begin reading that alert, it does not make sense to us. 

It would be beneficial to include a feature in Opsgenie where a label is provided with specific words for the alerts.

Opsgenie could refer to that one word rather than reading the full alert from beginning to end. 

Perhaps there is an IP, or an error has occurred, but it is not impressive to have Opsgenie begin reading everything. 

There should be a feature in which Opsgenie reads a label. That would be more appropriate.

A labeling feature would be beneficial.

I would like to see reports that can provide us with integration with Jira or with another management solution, which I'm not sure Opsgenie provides.

The integration is possible, however as Opsgenie reports is an area that needs to be addressed. An alert is received, and Opsgenie will immediately generate a ticket or card for that issue, track it, and provide a follow-up. Opsgenie will also track an issue's whole life cycle. This is something that I would like to see in Opsgenie.

Not just Jira. It's incident management since that's what we use Opsgenie for.

I would want to have an issue management solution that covers the entire life cycle. They will begin with Opsgenie and work their way to the end. 

To have Opsgenie follow up, perhaps by sending a communication to management that this issue is still not been resolved, or something similar. 

A report of the entire life cycle.

We are currently working with Opsgenie. The company has been using it for three years, or more. I joined the company later. I have been using it for two years.

Opsgenie is stable.

I have never had any issues with the stability of Opsgenie.

I can name one or two instances in which I did not receive an alert. But those notifications might be caused by an issue with my signal. 

I can't be certain that it wasn't an issue with Opsgenie. I can't say it's completely reliable.

Otherwise, the performance is amazing, in terms of stability.

I am not aware of any use scenario in which Opsgenie may send the same alert to two people or not at the same time. 

I am not sure, we have never attempted it. 

I have never seen something like this before. For example, let's assume you and I get a call when we are on-call. I am not sure whether Opsgenie can accomplish this because I have never seen it done before. 

We didn't have that use case, therefore we never attempted it. 

I am not sure Opsgenie can provide us with this option in terms of scalability. 

As just one individual will be required to be on each team. The call should only be received by one individual. There is, however, a process where you can add a few numbers. I can add your number, and my number can be added. Opsgenie is scalable.

We have more than 50 people in our organization who are using this solution.

Some are exclusively connected to alerts in terms of L1, the monitoring team, and the service monitoring team. Some are tied to on-call men, while others are just checking the reports.

Opsgenie is used by 50 people in total.

I have not contacted technical support. I have not had any issues where I have had to contact support.

Previously, I have not used other solutions. My experience has always been with Ospgenie.

I am working with AWS on the cloud side. I am using Terraform and CDK a little bit for infrastructure as code.

I am working on EKS Kubernetes, ECS Elastic Containerized Services, and Elasticsearch, which is now known as OpenSearch, from within the cloud services, ElastiCache, and Redis.

From my perspective, it is straightforward because we already have webhooks.

If I drill down to the high level, it may not be complicated. 

I believe it is straightforward.

I would rate the initial setup a three and a half out of five.

If you give it a three and a half, you won't need a consultant. To me, it seems self-explanatory. However, in order to use it, we must first comprehend it.

If I am not mistaken, we have the business edition which includes all of the features.

I am not aware of the cost, but it is available on the internet.

I can tell you that our upper management is pleased with the price. Because of the services provided by Opsgenie, I believe the pricing is reasonable. However, it is dependent on the other company. It's fine for my company.

I have never compared other solutions.

I would recommend this solution to others. 

I would advise the team or an individual to look into the reporting issue. It is a useful feature that most individuals do not use. It also provides a better understanding of how problems arise and how quickly they are resolved.

Reporting is a feature that I would recommend using more. It is not really valuable for our company since we have other processes in place to evaluate the report. 

However, I would recommend that you use Opsgenie.

I would rate Opsgenie an eight out of ten.

Our primary use case for this solution is on-call rotation, and we deploy it on cloud.

The solution has helped us stay alert on incidents and improved our response times. 

We have found the integration and alerting feature very valuable because it can page you when you are on-call. It is pretty helpful when we have production issues, and some metrics and alarms are configured for notifications and calls. Therefore, it alerts us so we can act when necessary. Additionally, the rotation and scheduling are beneficial.

Previously when we had issues, we would get a notification from Slack, but that wasn't adequate because it wasn't directly to the people on-call. It was just a notification and not a phone call, so it didn't help us because we could not write scheduling, override or get escalation for the notifications. With the service in this product, we can now respond to the incidents that it scales to our team, the SRR team and others. Hence, we know that someone is notified and can act on it.

The user interface could be improved.

We have been using the solution for approximately two years and are currently using the latest version.

The solution is stable.

The solution is scalable. Currently, there are approximately 80 people in our organization using the solution. In addition, around five people are required for deployment and maintenance.

I have never been in contact with the customer service and support team.

I was not part of the first integration but was involved in the integration for scheduling. I worked on defining rotation and creating new things in other rotations. It wasn't hard, but we had some minor issues getting it right the first time.

We implemented the solution in-house.

We have seen a return on investment in this solution.

I am unfamiliar with the licensing costs for the solution.

I rate the solution eight out of ten. The solution is good but the user interface can be improved. My advice to new users with this solution is to integrate as many tools and data sources as possible as well as some alerts and alarms tools.

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 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.