Splunk On-Call Reviews

• On-call tool
• Transmogrifier
• Third Party integration

It's provided real time incident management and alert paging via email, SMS, or call. It has also enabled duty rotation and operations management.

More support is needed for customization in the Transmogrifier for fetching dynamic content from URL.

I've used this solution for one year.

There were no issues with the deployment.

We had no issues with the performance.

It's been able to scale for our needs.

It's excellent.

We used SCOM before.

I implemented it myself.

We evaluated PagerDuty, but VictOps has a better overview of incidents as it has an incident timeline and Transmogifier tool.

Its the best solution of its type out there, you should go for it.

VictorOps is our alerting system for the on-call process. Our developers use this solution to be alerted when something goes wrong with our services. The solution is connected with our monitoring system.

VictorOps has decreased the meantime to acknowledge an incident management process. Our developers can be on-call faster when we are using this solution. We can fix our incident much quicker.

VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process.

At that stage, all our needs are fulfilled, but at the beginning, we had some feature requests and they were deployed during their roadmap.

I have been using VictorOps for approximately four years.

In the beginning, we had some minor issues with stability, but we do not face any issues anymore.

The solution is scalable.

We have approximately 300 developers using this solution. We have no plans to increase usage because it is working very well at the moment.

Many years ago, when VictorOps was a standalone company, when it was not part of Splunk, their support was more dedicated for us. We had a dedicated customer success team, but nowadays when they were acquired by Splunk, we are not at that tier level of dedicated support or dedicated customer success team. This is not good for us.

The implementation was straightforward. We had some minor issues and we discussed is with our customer success team and their support. It was quite smooth overall.

The whole process took us one or two quarters because we changed our internal processes at the same time. It was connected and we had that strategy that we started from one team, and then we roll out our idea to all teams in our company.

We did the implementation of the VictorOps with the help of VictorOps support.

This solution is part of our incident management process tool, and we only need a few people to manage it. These people are responsible for processes and responsible for this solution. We do not have dedicated people to maintain VictorOps.

The price of the solution could be less expensive.

We have evaluated other vendors before choosing VictorOps.

At that point in time when we were evaluating other solutions, VictorOps was a good fit for our needs. For example, we had a dedicated support customer support team. Individual treatment was good for us, a great price point. They are very flexible in pricing. In the end, the price to quality ratio was the best among the other vendors.

My advice to others is you should start small and then roll out to other teams.

Use a proof of concept, at the beginning. Find the first teams which can use the solution. Then you can roll out based on that POC experience.

The biggest lesson learned from using VictorOps was we change our approach to internet management after implementation. It was a part of a big change in our culture of modern incident management. 

I rate VictorOps an eight out of ten.