Opsgenie Reviews

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.

Opsgenie has been most valuable in managing our incident response. We use Opsgenie for on-call management of AWS services, and its integration with CloudWatch has been particularly beneficial. 

Opsgenie alerts us to anomalies in cloud services, not just incidents but also performance issues like delayed response times or execution errors. So, we will quickly know about the issue, and it allows us to take swift action. It has been very helpful to us. 

Opsgenie's strength lies in its configurable alerting levels, from first responders to escalation managers. It offers different levels of notification options, including WhatsApp integration, ensuring timely alerts to the relevant team members.

We also use the on-call scheduling feature. It is easy to use. The on-call scheduling feature is user-friendly and easily integrates with our existing systems, streamlining schedule management without added complexity.

I would like to see improvements in reporting capabilities that could provide additional value, offering deeper insights and analytics for our operations.

I have been using it for two and a half years. 

I would rate the stability an eight out of ten. I didn't face any downtimes or issues with stability. 

I would rate the scalability an eight out of ten. It is suited for multiple large teams, but I am not sure if it is suited for enterprise-level businesses. 

Opsgenie is the better one than PagerDuty. 

PagerDuty has acquired multiple products, and then it has tried to integrate the features, which is not always successful because they are not able to prioritize tasks properly, which feature to think about first, how we want to prioritize, how we want to improve, just lagging one back on the website, the product. Pricing was also a factor. Their customers were not getting the value.

Knowing the tool is required.

The pricing is fine. I would rate the pricing a six out of ten, with one being high price and ten being low price.

I would recommend using the solution. 

Overall, I would rate the solution an eight out of ten. 

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.

Opsgenie is just an out-of-the-box tool included with the Jira Service Management (JSM) package. When you're on a premium package, above the standard, Opsgenie is included for free. 

The integration aspect I'd associate with JSM for incident management, and possibly for tracking changes in performance, but it's definitely a critical component. Virtually all companies, if not all, would likely be using Opsgenie for this reason. 

There are also a few third-party apps I'm integrating with Opsgenie. I understand its importance, as it enables easy alerting on your phone among other features. It can also integrate with other service desks like Freshdesk or Zendesk.

So, there's quite a bit to it. It's a great tool, serving as a crucial pivot for responding promptly to Service Level Agreements (SLAs) and avoiding delays in response times of six to seven hours.

The on-call scheduling feature is essential. It's best practice to rotate shifts among team members, managed by team or group leaders, to avoid having the same person always on the night shift. Opsgenie automates this process, allowing for shift swaps and even temporary substitutions, such as covering someone's half-hour lunch break. This tool enhances visibility within the company regarding who is on call at any given time, making it indispensable for a busy service desk to maintain coverage, especially for critical roles, by facilitating easy ticket triage and call handling during absences.

Initially, Opsgenie had bidirectional integration with Jira Service Management, but that functionality has been scaled back. Previously, Opsgenie was adept at managing incidents within its ecosystem, offering seamless ticket transfers between Opsgenie and Jira Service Desk. I valued the ability to push tickets between the two platforms, addressing the need for widespread information accessibility, though it sometimes led to duplication. 

My suggestion would be to reintroduce complete ticket funneling between these systems to streamline operations.

I have experience with this solution.

Bitbucket tends to have the most downtime among Atlassian products, but the others, including Opsgenie, are quite reliable. I'd rate Opsgenie's stability as a nine or a ten out of ten. 

I would rate the scalability an eight out of ten. It's quite scalable, though there's always room for improvement.

Opsgenie provides value for any company with more than ten members, especially if operations are remote. For in-house teams smaller than five, it might not be as necessary. 

So, it's beneficial for companies with 10 to 20 members and absolutely for enterprise-level companies. Once you hit the 10 to 20 employee mark and start to scale, that's when Opsgenie becomes indispensable.

As a partner with Atlassian, we have a direct contact. However, our main point of contact recently left for a competitor, and our new contact hasn't prioritized us as before, affecting the quality of support. Though it was better previously.

Neutral

I've been an ITSM consultant for eight to nine months now, and I've done tech demos for two consoles, and I've participated in our ITAL maturity assessment onboarding a big insurance company to Atlassian.

I've done everything. JSM, Jira Service Management, Jira software, I've done Bitbucket, Opsgenie.

To properly set it up with directional communication, the initial setup could take about one to two weeks if you have everything you need. This includes organizing rotations for the companies and their product owners along with their teams. It's a considerable task, but introducing it team by team, depending on urgency, could streamline the process. 

Overall, if done intensively, two weeks should suffice to get everything in place, and then another couple of weeks for a testing phase to ensure rotations work correctly in real time. I'd rate the difficulty as a six out of ten, with ten being easy to set up. 

I did integration for Opsgenie as the integrator for my clients.

The pricing is on the lower side; I would rate it a six out of ten, with ten being low price, which indicates good affordability.

I've only used Atlassian products.

Overall, I would rate the solution an eight out of ten. I would definitely recommend using this solution. 

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 the product for email notifications from the automatic application.

Opsgenie has streamlined our communications and alerting.

The tool's most valuable features are text and phone call alerts.

The installation of other applications is difficult in Opsgenie. I would like to see more flexible reporting methodologies. Scalability and pricing also need to be improved.

I have been working with the solution for five years.

I rate Opsgenie's stability an eight out of ten.

I rate the tool's scalability a five out of ten.

I have not used Opsgenie's tech support.

We have seen ROI with the solution's use.

The solution's prices are exorbitant.

Opsgenie is a good product; you must be technologically savvy to use it. I rate it an eight out of ten.

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. 

The rotations are very useful for us, and the routing for alerts is also very useful.

We have the escalation feature, which is pretty neat, and the API is also pretty easy to use. Although it lacks a lot of features that we would like, it's pretty straightforward. So, if we want to do customizations and use the API along with Opsgenie, it's fairly easy to do. It's very well documented.

The API could use some work. It's the second time around or the second company in which I have had to work on some customizations using Opsgenie, and the API lacks a few features. It could use some work.

I would like to see a little bit more work in API key management in the Opsgenie UI. It's a bit difficult to manage sometimes. For example, in terms of management, you can either see all the keys or none of the keys. This is something for which I would like to have better granularity so that I could give some people access to some of the keys. It's something that I don't have today if I'm not mistaken.

When using the API at some points, on more than one occasion, Opsgenie gave me an error that was not really the reflection of the actual error going on. We had to spend a lot of time debugging and trying to figure it out, and that was a waste of time. We can't rely on the output that we're getting from the platform. This is a bit concerning. It's something that could use some work.

I'm not sure if this is already added, but the last time I looked at incident seeker, which was several months ago, it lacked roles during incidents. So, you have a person taking care of the incident, but you don't have multiple people with different roles during the incident. This is something that I would like to see, but I need to confirm this because the last time I looked into it was several months ago. We even decided to go with a different tool when I looked because I had to do an assessment and compare some of the tools, including Opsgenie. We decided not to use the incidents feature of Opsgenie because it lacked well-defined roles during incidents. This is something that I would like to see so that we could go back and consider Opsgenie as our management tool for incidents.

We have had some difficulty managing the people who leave the company. We even had to write a script of our own to control this because it doesn't seem like Opsgenie has a tool for turning off those users automatically. This is something that I would like to see in the future.

I have been using it for several years. I used it even before it was bought by Atlassian. Overall, I have been using it since 2013 and then there was this huge gap in which I used a different tool, but for the past three years, I've been using it again.

It's pretty stable. However, on some occasions, the error that Opsgenie gave was not really the reflection of the actual error, which is connected a bit to its stability because we can't rely on the output that we're getting from the platform.

It's scalable, but we do have a problem with the governance of the people who leave the company.

Currently, we have about a hundred users. We have plans to increase the usage. The company is growing, and we have a lot of teams that are not on-call at this point, but they will need to be. So, we are planning to expand.

It has been some time since we had the issue with the API message. If I remember correctly, we were not able to get quick answers. On the technical side, they probably didn't know that this problem was happening. So, the support was not effective for this issue specifically.

I also had to contact them once regarding configuration, and they were pretty quick to understand what the problem was, and they were able to help me. With regards to the configuration using the user interface, their support was pretty useful. It was effective, but with regards to the API, they were either not specialized or didn't have the answer. Both reasons are concerning.

I have some experience with PagerDuty. I used PagerDuty for about two years, but we hated it, and we went back to Opsgenie right after. I'm not sure if that's the case anymore, but PagerDuty was less expensive. That was one of the reasons why we left Opsgenie and moved to PagerDuty. There were also some things that Opsgenie didn't do. I started working for that company after this decision was made. So, I'm not sure about all the details of why they decided to leave Opsgenie at that time, but they did leave Opsgenie, and after almost two years, they decided that the PagerDuty was not good, and they went back to Opsgenie.

One of the reasons for going back to Opsgenie was that PagerDuty had fewer features than we were expecting. If I recall correctly, the main reason was the fact that the provider of the Terraform for PagerDuty was not well-maintained. We had a lot of issues with it, and in our case, we were managing everything as a code. So, it was very important to us that the provider was correctly maintained and had fewer bugs. This was one of the strongest reasons if I recall correctly.

Onboarding people into it is pretty straightforward. Because we use it as a service, we didn't have to do any deployment or any configuration other than the configuration that we had to do for the teams. So, in terms of deployment of the tooling, we didn't have to do anything. In terms of configuring it to work for our needs, it's pretty straightforward. It's not complicated.

For the current company I work for, it was configured by a different team. So, I don't have information about the number of people involved in its deployment. I haven't participated in the configuration for the whole company. I was only responsible for configuring a new team, which was pretty straightforward.

In terms of maintenance, because it's a service, we don't do any maintenance. The only maintenance that we do is our internal one because we use Terraform to build teams. So, this is the only maintenance we do, but it's not really of Opsgenie.

In the company I'm working for, currently, we are using the standard edition of Opsgenie. We're paying around $3,000 a month. It's a bit expensive compared to the other tools we use for different purposes. 

We find it a bit expensive because although Opsgenie is a complete tool for monitoring, it does not provide us with everything. For example, even though Datadog is for different purposes, we get a lot from Datadog. It's a monitoring tool, and we have a lot of things going on there. There are a lot of things that we use. We heavily use it, and its pricing, in the end, is a bit similar to Opsgenie, but Opsgenie offers much less because it has a closed scope. Overall, we're happy with it right now, and it's not a big deal, but it was one of the reasons that a different company decided to leave Opsgenie.

I don't know if everything is included in the cost or if there are additional costs. We pay for users, but I'm not sure if that could be considered as paying separately because if we add a user, our bill will grow invariably.

We pay for seats in Opsgenie. It's a subscription with a set number of users. It's a bit annoying that when we want to add a new user, we have to come and change our subscription and then add the user. I understand this is a safe option, and you don't charge your client without their knowledge, but at the same time, I would like to see an option that allows it to be scaled automatically without having to change our subscription every time.

I would definitely recommend it for a medium or a large company. I've seen it being used in small companies as well, but I'm not sure about the return in terms of money because it was too expensive. In one of the companies, we used it before it was acquired by Atlassian. At that time, the company had 30 people. It was a very small company, and even though we had Opsgenie, it was very expensive. I remember this being a recurrent topic in our meetings.

I would rate it 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 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 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. 

One of the features my team found valuable in Opsgenie is the alert. There's also the option to install an app on your phone, so even if you don't have any mobile reception, but you're still connected to WiFi, you still get the alerts via the app, not just via phone call or SMS. The combination of both options was very useful because sometimes you have data and you don't have coverage by mobile, or vice versa. To have both options in terms of receiving alerts was very useful. 

Another valuable feature of Opsgenie is the on-call rotation with alerts. I belonged to a small team of three, then the team expanded into four members where everyone was on a weekly on-call basis, with each team member having a week of being on-call. At first, it was once every three weeks on-call rotation, then it became once every four weeks, so the on-call rotation with an alert feature was useful.

My previous company had two separate environments, on the cloud and on-premises. My team was in charge of the on-premise environment, so there was a queue for my team with everything in Opsgenie, then the DevOps team had its queue on a group of infrastructure related to the cloud. Each team had its own devices organized in a group that was only managed per team. The on-call rotation was also separated between groups. Opsgenie is a very convenient solution for both teams in my previous company.

When I needed to add the fourth guy to the on-call rotation, I had trouble finding the option in Opsgenie where I can add the new user. It took me some time to figure out because the icon was very small. You have a pencil icon that you need to click, but it was so small and in a place that wasn't so obvious, so this is an area for improvement in the solution. I couldn't find the icon myself and my manager had to show me where it is. Opsgenie needs to be more user-friendly, particularly when it comes to finding the "Add New Users" option in the on-call rotation feature. Other than that, the solution was very easy to use, and you can see both the open and closed alerts.

I no longer use Opsgenie, and the last time I used it was at the end of February this year. I used Opsgenie for more than three years in my previous company.

In terms of stability, I don't remember ever having a problem with Opsgenie. In the three years when I've used the solution, I never had an issue with it.

In terms of scalability, for example, adding a new user to the Opsgenie on-call rotation feature wasn't difficult. It was finding the option that was difficult, but once I found the button, it was very simple. It's just about the visibility of where the button is. Opsgenie scalability in terms of adding new devices to monitor, or having one monitoring server on-site connected to Opsgenie, then moving the server to another location by modifying the configuration on Opsgenie to the correct IP address, then moving to another on-premise solution, required my team to reconfigure Opsgenie to use that new server was pretty easy, with no problems. Overall, the scalability of the solution was very good.

As far as I remember, my team never needed to contact the Opsgenie technical support team. 

Positive

Before that, I worked at a company where we used a different solution which is called Pingdom, which is a Swedish company. Then later acquired by Austin, Texas-based SolarWinds. Pingdom is now part of SolarWinds, and it's a monitoring software as a service, so it's similar to what Opsgenie does.

I also used SolarWinds Orion, which is the leading on-premise software for monitoring and making backups of configuration files from on-premise devices. It also sends you alerts when something is done. SolarWinds Orion gives you more than just monitoring and alerting, because you can also set it up to back up the configuration on each of your network devices. This is an added value that doesn't exist in Opsgenie. 

If I compare Opsgenie to Pingdom, which is a cloud-based software as a service solution as well, Opsgenie is competitive and is either on the same level or even better than Pingdom. 

Though I wasn't the person who implemented Opsgenie, to begin with, and I cannot say it's one hundred percent, but I'm pretty sure the initial setup for the solution wasn't so complicated. I only needed to add a new user or add more devices to be monitored during my work in my previous company, and it was pretty simple to do.

During my work period we only used the in-house resources. 

Taking into account that Opsgenie "saved" many devices in our environment from getting overheated, which would have caused a major outage in our HQ offices, I believe the monthly subscription cost was way lower than the return. 

I'm not the person who dealt with Opsgenie in terms of pricing, and I don't know how the solution compares to other solutions in the market, price-wise. I won't be able to say if it gives you the best value for money or not, but if Opsgenie gives good value for money, then I don't see a reason why you shouldn't use it.

When I started working for that company, Opsgenie was already being used. 

My advice to people considering the use of Opsgenie is that first of all, every normal company that has critical infrastructure needs a tool such as Opsgenie or a similar solution. I'm not saying buy Opsgenie or buy a competitor, but it's definitely a tool that's required. 

I recommend asking for a POC (Proof of Concept), and I would suggest that you also have a meeting with Opsgenie presales engineers. You should familiarize yourself with the solution and understand its capabilities, then if Opsgenie sounds right for you, including its price, ask for a POC. Usually, you're given two weeks or one month for free. You get free usage of all the components that you want for that time period, so you can experience it and see how you can configure, manage and use it for monitoring. After you do the POC, you can decide if you want to continue with the solution or not.

My rating for Opsgenie is eight out of ten.

The company I used to work in was a customer of Opsgenie.

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.

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.