ITRS Geneos Reviews

It's a monitoring tool. It's watching for all of our alerts, including high use of the server or running out of memory.

It's catching things that are going wrong before they become catastrophic, in most cases. It helps us avoid long periods of downtime and gives us a view into when things aren't quite working properly so that we can get in and fix them. We've seen those benefits from the day it was implemented.

One of the best aspects of Geneos is that it has a broad scope and can cover a lot of use cases. You can write your own scripts to monitor really specific things. And the rules that you can put in place can be quite complex for the alerts. Those two things are quite good.

The deployment method for upgrading is a bit tricky. It takes a little bit of manual effort. If that could be a bit more automated, it would help us a lot.

I'd also be interested in seeing some intelligent analysis of log files, along the lines of AI. It would be nice if it could start correlating events from all over the estate.

I have been using ITRS Geneos, in different companies, for about 15 years.

It's fairly reliable.

There are always glitches, but they seem to be fixed reasonably quickly. And, in general, it does what it says it's going to do.

Once you've automated it, it's very scalable.

For us, the hardware is in London and the solution is across multiple departments. We have about 30 to 40 users.

I expect our usage will remain steady. We are changing our platform, but it's the same size as the one we're on now.

The support is very good. It's quite immediate. I don't think I've ever had an issue that hasn't been resolved.

Positive

What we had, and still have, was more low-level than what I would have been involved with. It would have been more on the operating system level.

We added Geneos because we needed more visibility into the application. The other solution only looks at whether the machine is there and running or not.

The initial deployment can be complex. It depends on how much you want to get into it. It's the sort of thing that grows organically. If you have a problem, you then add some more features to cover things so that you don't have the problem again. But when you first implement it, you will probably make it quite simple.

Including the provision of the hardware, it takes a couple of months to deploy. It's just a matter of installing the system and getting all the networking working.

The number of people required to deploy the solution depends on the size of the organization. For my current organization, it would take a couple of people to do it.

Maintenance involves upgrading it every now and then. License file replacement is another task.

Our biggest ROI is that it has saved us downtime.

The pricing seems reasonable. We're happy enough with it.

There are a number of add-ons that come with extra costs. We use some of them. We have a license now in which most of the features are included, but there are some special extras that have to be added on.

Do a proof a concept and definitely look at how quickly other systems alert when there's a problem. With Geneos, it's pretty instant. With some of the other solutions, it's not that obvious, and can be a number of minutes before you get an alert.