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. 

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.

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.

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

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

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

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

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.

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

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. 

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. 

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.