ITRS Geneos Reviews

We're able to highly customize the integration of custom developed monitoring samplers.

After developing of a lot of custom samplers integrated with our software, it gave us the opportunity to act proactively to identify malfunctioning applications and services. This allowed us to minimize the business impact when we had network issues.

There is a lot of functionality within the product that can be implemented in many different ways. It would be useful to restrict the way to apply some conditions and for it to have more out of the box rules. It would also be nice if it offered more flexibility and the possibility to aggregate data.

I've used 2011.2.1 (Gateway version) and ga-3.0.22 (NetProbe version) for about three years.

There were no issues with the deployment.

We had no issues with the performance.

It's been able to scale for our needs.

They're very good and are always available to help us with the implementation of new solutions.

Not at the customer where I’m working at the moment.

I didn’t configure it myself during the initial setup. However, I did try it on my own in a virtual environment and I can say it was very simple to install.

It was implemented in-house.

It’s very easy to install and setup, offers high scalability, and has a low resource use.

The visualization layer and the config editor (with host of out of the box plugins) that makes setting up monitoring on any application quickly and efficiently covering infrastructure and more detailed monitoring points like middleware, messaging and database.

It has helped us re-define the Monitoring operating model which in turn has made support teams more efficient by using features like commented snoozing on various levels, use of knowledgebase articles associated with each alert cell, metric logging for capacity monitoring etc.

I would like to see more integration support via use of APIs. They have released openAccess for the same but hasn’t really picked up. Also, more flexibility in creating own customized plugins (not just using toolkits) and deploying on agents. Also, more data analytics capability would be helpful.

I've been using it for six years.

There is are issues with the compatibility of plugins with AIX servers.

There were performance and stability issues in running gateways and net probes on Solaris servers.

We have had no issues scaling it for our needs.

Customer service response is really good through raising tickets on their online support portal.

They generally respond within couple hours for a normal ticket and can respond even urgently depending on the level of escalation. They are happy to come on site as well to work on bigger or more specific issues.

The reason for choosing ITRS Geneos was the availability of its wide range of out of the box plugins and its visualization layer that simplifies and represents the application components well.

The process in itself is simple to setup but getting it working through the corporate securities and restrictions can be a pain, but I guess that would be the case for any new tool setup.

It is a bit expensive so it may not be feasible if you are planning to use it for a specific application(s). But if you use it across a range of applications (like within a whole department) then look to combine the licenses and then it can be really worth the money. Moreover, this way it standardises the monitoring platform to have consistency across teams and set up a standard monitoring operating model.

It may be tempting to get it working quickly using the root, but I would highly advise against it. Create a new user and give it appropriate permissions by identifying what access it may require to run plugins. Due to its ease of usage it can be abused by application support teams so I would suggest to review the setup regularly and make sure there is only 1 or 2 admins changing and updating monitoring otherwise it can get quite messy very soon. Try to rely on watching the visual interface and not on emails as that can grow huge as well. If you do stick to only absolute critical ones.

Try to pilot the project in a small area and learn as much as you can before deploying it across a wider estate. Use ITRS support as much as you can at least in the beginning. Also, have a experienced Geneos professional implement it.

We have automated some manual system checking processes.

We have monitoring tools that allow us to view individual systems health and issues on its own.

Geneos gives us visibility on all of our systems at once and we can build dashboard views to monitor transactions moving from one system to another. This has greatly assisted with troubleshooting and helped us understand how the system behaves when issues are imminent leading to proactive prevention.

• Custom script toolkits
• Data aggregation
• Alerting rules to emails
• System APIs

Backward compatibility with deprecated features and in system documentation on what configuration areas are needed to be updated: There is a bit of this in place already, but it can be improved.

I've been trying to update to version 3.5 but the gateway will not start up because my configuration contains deprecated features. The error logs are not very helpful and I've been using a tedious trial-and-error process to find out which part of my configuration is disagreeing with the new version.

I could start with a lower version and then work my way up but that would mean upgrading over 50 servers multiple times which is something I'm trying to avoid.

Technical support is great. They have an online ticketing system for support. I find them quite responsive any time of the day.

This was the first product I used, so I do not have a comparison.

The initial setup was done by the ITRS consultants. They designed a fully customized solution for our system. The basic out-of-the-box monitoring is quite straightforward. The custom solution involved uniquely written scripts to read our application log files.

We started with the vendor team, and then they handed over to me and I became the in-house team. A tip would be to have a dedicated team and give them time to play around with the program. Try all of the features and settings and ask a lot of questions. Geneos has a lot of features and it grows very quickly. Geneos is very flexible. Be sure your Geneos team has a balanced skillset; creative skills as well as technical.

I don't have the figures unfortunately. But the ROI has been growing slowly. We do have a number of other tools and our systems are quite big and complex. I've also met some resistance in the adoption of another monitoring tool from the users. Expect a slow start on ROI with Geneos. In my case, it is finally gaining popularity after catching a number of critical issues that their other monitor tools missed.

It's a lot of work to get started but worth it.

• Excellent set of plug-ins for the financial industry.
• Easy to extend and to incorporate existing monitoring scripts/programs.
• Publishing monitoring data to many users is simple due to webservers included in Geneos.
• Attribute-based viewing tree allows different views of your data for different purposes/users.
• Very good maintainability due to groups/types: very effective build and change of configuration.

• Trading desk has continuously updated view of full quotation process. Issues are displayed and alarmed about in near real-time instead of going unnoticed for longer periods of time.
• Depending on the issue, the relevant group of people is informed in case of a problem and has already a head-start due to the specific information sent by the monitoring system.
• All teams (operations/IT management group/users) have a common information base consisting of the generated dashboards and drill-down web pages leading to each running sampler. This immensely improved communication in case of production problems.

5 years

No issues. Deployment is very easy also for large number of hosts due the feature of "self-announcing netprobes". This makes it possible to deploy to hundreds or even thousands of servers without manually configuring the connection between monitored server and Geneos gateway (where all data is sent to for evaluation).

No issues.

No issues. If a gateway has a high load it easy to set up additional gateways to get headroom on each gateway again. If a netprobe has too many servers one can parallelize by running several netprobes per monitored server. Resource footprint of Geneos is generally very small.

Excellent. If you address to the help desk you are immediately in contact with very knowledgeable personnel. There is no "first-level" support which can only handle easy problems. You can get right down to the issue at hand without being transferred (see tech support).

10 out of 10. Service requests are usually acknowledged (by humans, not mail robots) within minutes and answered depending on the difficulty of the question but mostly within 20 minutes, often faster. The quality of the service is very high. You get code examples or links to the relevant sections of the large body of online documentation (videos, manual etc.). If needed your configuration files are proof-read and possibly corrected.

We used Icinga (a Nagios-Clone) before and currently still do in various areas. Geneos has been introduced due to the need for real-time monitoring and notification and for the excellent possibilities to publish monitoring results via web servers.

Initial installation was relatively easy even though - due to the nature of the task - numerous components had to be installed: netprobes on every monitored server, gateway servers, dashboard webserver, webmontage webserver. Directly after installation, however, basic real-time infrastructure monitoring worked out of the box, more advanced monitoring after appropriate configuration.

We had partial support for specific monitoring requirements by ITRS professional services staff on-site. They all were very knowlegedable and customer-oriented. It was obvious that in addition to solving the task given to them they really tried to transfer their knowledge to our staff.

Difficult to quantify. We have reduced stress level of all involved personnel and increased user satisfaction due to the real-time dashboards we gave them. Targeted notifications reduce effort due to false or misdirected alarms. Processes have been improved due to the insights gained by the Geneos monitoring.

ITRS is quite flexible depending on the size and requirements of the customer. Given the benefits we have from Geneos and also compared to pricing of other solutions (e.g. job scheduling) costs have not been an issue so far.

Icinga (Nagios-Clone), AppDynamics, BlueStripe, Leutek. Icinga was too slow for our requirements and would have required - according to the company mainly supporting this open-source solution - major development efforts to accelerate it enough. The other solutions did definitely make a good impression but we went finally for Geneos due to its specific focus on the financial area (we are a bank) and also due to positive experiences with Geneos we had in the past in another time-critical business area (ETF Market making).

For the beginner there is a steep learning curve. To master the Geneos technology reasonably well, four to six months are realistically needed (within those you can already build up an initial monitoring though). For larger organizations it may make sense to centralize this know-how and re-use it for different monitored applications or processes instead of having many individuals learn about Geneos just to realize one specific monitoring each. Once set-up, Geneos proved to be a very powerful and versatile tool to real-time monitor our IT infrastructure and - most important for us - our critical applications and business processes.

Event Management: Manages alerts from infrastructure, applications, and batch jobs. Performs 24/7 monitoring across our Global Markets platform.

This solution has helped provide relief to existing Level 2 teams, allowing them to focus efforts on in-depth problem analysis.

• Dashboards
• Processes
• FKM
• Disk

These alerts proactively help manage the enterprise operational risk.

A lightweight version which could host more than 100 gateways, as we can see slowness while loading all our gateways. We do support a horizontal platform and having this feature will have an impact in the MTTR.

Our primary use case is to monitor services and networking. We monitor applications like the processor, CRM, and next-gen Gateway which is a Windows service.

Geneos is responsible for collecting and monitoring data from our computers. It's helpful for us to get data and to get good information about the health of our systems. The data it provides is very helpful for us and for our work.

ITRS Geneos provides peace of mind by mentoring our processes and applications. It's in the most amounts of environments. Geneos has encouraged real-time analysis and monitoring.

Geneos is very easy to use. They have an interesting dashboard and the app's console is very easy to understand.

It's also easy to implement. The implementation of Geneos is very easy and interesting. It's not complicated. It's very quick to implement. The installation is very easy. There are many topics about ITRS Geneos that explain more about the features of the function of Geneos. 

The architecture is very comprehensive.

It provides us with real-time data. We use the dashboard, we can remotely monitor the services, and we can reach the data, the percentage of CPU and memory with real-time monitoring.

We previously used Nagios. It would take us thirty minutes to get an alert. With Geneos, you can use the access time so we can monitor the analysis and we can receive the analysis when we want and with what we want, every 15 minutes or 10 minutes. With access time it is a very good way to monitor the alerts, to receive analysis. We also get alerts based on real-time data. 

There is a part of the rules for monitoring alerts. I want to understand more about how to choose the samples and the requirements for the rules. That is the part that I want to understand better and get better training for. 

I have used Geneos for six months. 

It's stable. If it goes down, we can use the Geneos backup.

We have around 100 devices that we are monitoring. There are three administrators who administer it. 

Their support is very proactive. When I raise a request, I have an answer immediately. They explain the solution very well. They provide us with a good way to research the information. I like the technical people who work at Geneos.

I worked with other monitoring tools like Nagios and I found Nagios is a bit hard to enter in the agents and to understand the services. But Geneos is very easy and it's very interesting to understand and to work with it.

I work with Geneos now because I switched companies. 

The deployment took around one hour.

We have not seen ROI yet. 

I think Geneos is really expensive, even compared to Nagios.

If you want a critical, secure, and regulated environment and to do powerful and flexible rules, you should choose Geneos.

I would rate Geneos an eight and a half out of ten. Not a ten because when the Gateway was very overloaded it was very hard to monitor the alerts, especially for the product services. The situation would be very critical. Otherwise, it's a very good, excellent tool.

For supporting market data organizations, Active Console & Gateway helps to diagnose problems quicker allowing timely incident notifications. Market data delivery systems are allergic to missed data which can be hugely detrimental to the business. The ITRS Geneos system assists engineers by allowing them to focus on troubleshooting the root cause instead of spending an unnecessary amount of time determining the impact of the problem.

Real-time monitoring of market data components on an enterprise environment is the most valuable feature of Active Console and Gateway. The built-in plug-ins allow administrators to easily configure monitoring components for market data systems such as Thomson Reuters Enterprise Platform and SRLabs Wombat (formerly NYSE). The interface is easy to use when interrogating monitored systems, viewing and graphing historical values, and performing Gateway configuration updates. Script generated output can be modularly added to allow greater insight if built-in plug-ins are not available.

Better exportable reporting of historical data would greatly improve the product's usefulness. Much of the reporting outside of the user interface is very basic and requires much customization to be useful. Additionally, the product documentation could provide more detail on plug-in features by showing implementation examples.

Take advantage of the "Hot Standby" feature on the Gateway product to increase resilience. It provides administrators the ability to configure a pair of Gateway instances with mirrored configurations for fail-back capabilities when hardware or network failures occur.

It's been able to scale for our needs.

Excellent 10/10 Any issues are addressed by ITRS support expertly and in a timely fashion.

The deployment is easy and the configuration is fairly straight forward. The documentation for plug-in configuration is a little sparse, but the latest version of the user interface is very intuitive. It is important to note that Gateway configuration accepts XML files allowing easily transferable setups.

In-house. Be sure to read the available documentation and, if possible, attend the vendor provided training and certification.

The product is priced quite high. There are pricing options for customers based on the size of the environment and plug-ins used by the monitoring system.

The product is renowned for its versatility for monitoring market data environments. The built-in plug-ins for TREP and Wombat is the main reason for using this product. The licensing cost is the biggest detraction, but cheaper solutions are not as robust.