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.

The on-call scheduling and the alerting. It completely changed our organization as far as recognizing system-generated alerts and responding to them.

We have a hundred licenses. I have 93 users in the system right now. All of our teams that have on-call resources are using VictorOps with rotations, schedules and escalations set up. This way, our monitoring systems can use route keys to route alerts to the proper groups for escalations alerting. Typically most alerts go to my Tier Two SysOps team for initial triage, and then if they need to escalate to a Tier Three enterprise resource provider, the database, Windows OS, Linux OS, or network people can then reroute the VictorOps ticket to them. The value of that is that obviously once that reroute happens the alert starts paging the on-call guys within the appropriate group. This has helped us to drastically reduce our acknowledgement time.

My VP of Operations is ecstatic about the VictorOps product. He has visibility into what's going on, and he can tell that folks are responding to alerts. It drives a level of responsibility. We used to have a problem of folks who would be an hour from their computer when they were on-call. We don't have that problem anymore, because our escalation schedules work, you have the on-call user, the next user in the rotation, their manager, and if they don't all acknowledge, it goes to the VP of operations, and you really don't want him to get your page.

It's driven a level of accountability. When folks are on call, they're responsive, they know that the mean time to acknowledgement timeframe is being looked at and monitored. That's a hugely important aspect of the product. It drives accountability and visibility of mean time to acknowledgement, which is the first piece. The sooner you acknowledgement you have a problem, the sooner you get to the mean time to repair part.

In reporting, being able to group by alerts and group by products would be good. They should put this in the titles of the alerts that come in, and make the report a little longer or a little more granular. With some of the reporting areas, we'd like to see some improvement with incident trends. Incident frequency kind of gets in that direction, but with incident frequency, you can only can move it around and it needs work. Also, being able to retain data for longer.

The other area is in the Timeline, being able to back up through the Timeline a little further and easier would be helpful. Of course, you can always do a post-mortem report to get there.

Generally, me being operations manager, I'm always interested in getting data out of the system as far as reporting goes, because I have VPs and CIOs that are asking for data, so I might be a little biased towards reporting improvements.

The other input I would have is in the users' area, when you're in Settings. The ability to search for a user by name would be handy, because you get a list of folks there, and sometimes it's hard to sort through that, so if you had a search box for users, that would be awful handy, especially when you get out to a hundred users, trying to scroll through a list of a hundred users, trying to find the one you're looking for. If it was a text sensitive text box for searches, type in "AR" and it starts filtering it out for you, that would help.

We went into production on the first of October, and we had been working with VictorOps probably 45 days before that. That would mean we've used it in total since roughly the middle of August of 2015, so about ten months.

It's absolutely been a stable product.

We have scaled from our initial deployment of 40 users and 22 applications being monitored by two different monitoring products to having SolarWinds, AppDynamics, Nagios, select servers, Splunk, along with Oracle OAM and IBM's Sterling Gateway, and a couple other systems that are generating alerts into VictorOps. We've scaled the amount of systems that are pushing alerts into VictorOps and have scaled all the way out to almost a hundred users.

The guys at VictorOps have been outstanding as far as support goes. They've bent over backwards to work with us and help us along, when in fact you can just go to training. I had 40 users here a month ago or so, so the support is outstanding, and the reality of it is, I looked at two other competitive products to VictorOps before I chose to go with them, and a colleague of mine who is kind of doing the same job but at a very large security company pointed me in the direction of VictorOps. I got onto WebEx and did an online demo. The price is attractive, it does what we need it to do, and it's been a great choice.

We were previously using one of the big house APM suites. We were using HP OpenView, so Operations Manager would have been the single pane of glass, so to speak, and we chose to move away from the HP product as far as our monitoring goes and dealing with system-generated alerts, simply because it took too much time and effort to manage the APM platform. It wasn't stable, it was complicated, it wasn't user-friendly, so we restructured our whole APM program platform, and VictorOps became one of the pieces of that.

I would advise you that it was a good choice for us to use VictorOps over a couple of the competitive products that we looked at. The price is very attractive, and the VictorOps folks have been outstanding as far as support goes. You don't feel like a number like with some of the larger companies. The support folks know me by name and the spirit and the culture of the VictorOps company is outstanding. Their customer service is good and the product speaks for itself. It does the job that it's designed to do. The support of the product by the VictorOps folks is outstanding. I would definitely recommend it.

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