Splunk On-Call Reviews

We are very satisfied with the tool. We were using a similar tool, but the features were not enough for us. I did some research and found VictorOps, which we then tested. It was perfect, so we decided to go for it.

My team as well as other teams are now using the tool. As for me and my team, we use it mainly for our phone alerting. If there are a few non-critical incidents, a notification is sent to VictorOps which converts it to an email notification and then to a phone alert.

One thing which we would like is an improvement to the history log on the main page. There is some history, and I think you can filter it, but the filtering options are not sufficient for us. We would like to have more options. You can find some history records for the previous two or three days, but you cannot dig into them. For example, you cannot find logs that are a week old. Another example is that you cannot check the incidents created in VictorOps from the previous Friday. This is one limitation that they need to fix.

When I plan according to the schedule in the platform, for some reason I'm sometimes not able to change the on-call duty person. For example, if I want to remove a person who is currently on-call and assign the on-call duty to someone else from my team, it's not possible. I need to log out and log back in first. Maybe it is browser-related, I'm not sure, but this is something that causes me difficulties from time to time.

Eight months.

I appreciate that whenever we have an issue, we have very good support. If there is something wrong, I always have somebody from VictorOps support to step in and help us out.

It was email2form, which was not a professional tool. From time to time the tool didn't work and when it was down it was a big issue for us. If tool wasn't working, we didn't actually have a phone alert, so we didn't know that there was a critical situation. With VictorOps, whenever there is a critical incident we have a phone alert.

I was in touch with the support center of the previous tool and they were terrible. Now with VictorOps, we create support tickets (via VictorOps as well), and the response time from support is always very good. I usually have updates within 24 hours of logging a ticket, which is something that I appreciate, and need.

It was not very difficult, and user account enrollment is very easy. What I like, is the feature where you have an account created in the platform, then you assign a phone number to the user, and then you can very easily test it. You send a test SMS and/or phone call to make sure that the person who will be on-call will receive the call. This is a very nice feature in the platform with the initial setup, because we use this tool to monitor other tools.

It depends on your requirements and expectations. You need to be sure of what you need and what you would like to use the tool for. Eventually you can find other tools on the market which might be a better fit for you, but for our purposes which I described, VictorOps is very good and even for the price we paid, it's perfect.

What was very good is that from the beginning, our VictorOps an account manager, has been working with me almost every day. Whenever I ask for support, he organizes a call and gives me access to a Sandbox, or a testing environment. I would advise any potential user who would like to investigate VictorOps to start using that.

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.