We performed a comparison between Opsgenie and Splunk On-Call based on real PeerSpot user reviews.
Find out in this report how the two IT Alerting and Incident Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Opsgenie has streamlined our communications and alerting."
"This is a scalable solution. I would rate it a nine out of ten for scalability."
"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."
"Opsgenie is easy to configure and use."
"The rotation and scheduling are beneficial."
"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."
"The integration feature is the most valuable. It provides a lot of customizations for the integrations we use."
"The most valuable feature is the ability to automatically create a ticket for the support team when there is an alert."
"The alert calling feature is the best because notifications are delivered via phone messages."
"The most valuable feature of the solution is helpdesk escalation."
"The flexible schedule is the most valuable feature. It was very easy to set out a rotation."
"VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process."
"Transmogrifier and automatic solution report gives me a report with the solution and the way to solve issues when an error occurred."
"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 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."
"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."
"The user interface could be improved."
"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."
"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."
"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."
"They could introduce many more features."
"The third-party configuration tool could be easier to use."
"Should have more YouTube webinars."
"At that stage, all our needs are fulfilled, but at the beginning, we had some feature requests and they were deployed during their roadmap."
"There could be improvements with communicating an incident or alert."
"The solution can be improved by including a wider list of permissions."
Opsgenie is ranked 2nd in IT Alerting and Incident Management with 14 reviews while Splunk On-Call is ranked 8th in IT Alerting and Incident Management with 10 reviews. Opsgenie is rated 8.0, while Splunk On-Call is rated 8.6. The top reviewer of Opsgenie writes "The price is competitive and it's easy to use and configure". On the other hand, the top reviewer of Splunk On-Call writes "Allows us to create flexible schedules for on-call rotations". Opsgenie is most compared with PagerDuty Operations Cloud, xMatters , Everbridge IT Alerting and BigPanda, whereas Splunk On-Call is most compared with PagerDuty Operations Cloud, New Relic, Everbridge IT Alerting, xMatters and ServiceNow. See our Opsgenie vs. Splunk On-Call report.
See our list of best IT Alerting and Incident Management vendors.
We monitor all IT Alerting and Incident Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.