ITRS Geneos vs Zabbix comparison

"One of the most valuable features is that it can be configured by non-developers. It doesn't require development expertise to configure it."

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

"ITRS can define rules to alert when certain parameters that you monitor breach a threshold. Rules can be configured to fire recovery actions automatically to clear the alert"

"ITRS uses SNMP to communicate with our devices as well as SNMP net probes installed on our servers."

"Geneos automatically sends email notifications when any batch job fails, the database is down or the website is down. It is automatically monitoring everything and reduces manual effort."

"It's a very powerful application monitoring tool across the industry. Many free, open-source tools are available. There are also paid tools, but ITRS Geneos is a real-time application monitoring tool where the user can monitor, self-configure, and manage alerts through their console."

"Tons of default modules which are available out of the box"

"The great advantage of this tool is real-time monitoring."

"The best feature is that Zabbix can report everything, and everything in Zabbix is free."

"We like the user-interface for this solution, which makes it an easy to use tool."

"The initial setup, while not simple, is easier than other products."

"The most valuable feature is network traffic monitoring."

"Zabbix is an excellent performance monitoring tool."

"The level of discovery-based configuration that lets us auto-configure the monitoring for various systems is a valuable feature."

"The most valuable features in Zabbix are those that help us overcome bottlenecks in CPU usage, as well as reduce memory delay. I know that we have only reached the tip of the iceberg of what Zabbix's features can do for us, and we have not used all of them yet."

"The flexible licensing model is one of the solution's most valuable aspects. It really allows for great flexibility for companies."

"A lightweight version which could host more than 100 gateways, as we can see slowness while loading all our gateways."

"Data visualization – real time and historical – is a weakness."

"I would really like to see something from the Geneos side to set up automated reporting from ITRS. We have to send reporting to management every day. To do that we have to check the dashboard and then we have to report whether everything is fine or not. In the future, I want something, some reporting kind of feature in ITRS, where it can collect all the data and mention what is green, what is amber, what is red in a report."

"One area where there is room for improvement is the log file. I would like to be able to do a pre-run on the log files. When you are testing log files for regular expressions, it would be good to be able to do a quick check up front on that side of things before you release that into production."

"We all look at the same things - CPU, disk space, paging stats, service status with RAG status on each. That could be provided straight out, saving significant time."

"​It needs to be easier to configure, especially with the JMX plugins.​"

"The ITA, the post-incident analytics, could be improved."

"I would like ITRS Geneos to develop an app, where instead of going to specific login terminals or logging into laptops or desktops to check alerts, we can have visibility in the app itself."

"Its UI needs to be improved a little bit more so that an end-user is also able to handle it. I can handle it, but others should also be able to handle it in a better way. It becomes complex when we are growing and need to add proxies. We need more scalability features and documentation for different use cases. A lot of articles are available, but they need to be in proper documentation. For example, when you have thousands of servers that have to be monitored in different regions of the world, there should be some kind of documentation to describe how you can create proxies and add them. Sometimes, when you are using the database, it can get overloaded. When the network is growing, the number of transactions becomes very high, and the database gets overloaded. There should be information about how to reduce the load on the MySQL database, which is what Zabbix is using. The market is growing a lot, and it should be enhanced for a lot more things. We are currently bringing enhancements at our end for different use cases. For example, when dockerization is going on, how can we check the logs inside the Dockers. We should also be able to monitor and check the number of logins and add features such as SSO login and two-factor authentication as a protocol. These are the security features and concerns that we have to deal with. Currently, we are developing modules to add features to Zabbix, but they should also work on these features."

"When using this solution in enterprise monitoring, you are able to see that there are some issues with equipment that could be causing a problem. Sometimes you want to make a root command that you do not want to be executed automatically. What we have tried to do is open an SSH session directly from the solution's interface but it is not possible."

"The System Center Operations Manager can be improved."

"They should open an SSH session from the web interface."

"I want Zabbix to improve the UX/UI. Zabbix doesn't use a JavaScript chart for images, and I want them to improve this."

"Sometimes, the documentation is a little bit written in Estonia – a country in Europe. The language barrier and translation to English can sometimes make it difficult to understand what they're trying to get at. It's just a language thing."

"To improve Zabbix, adding more features to support the monitoring of modern workloads like containers would be beneficial."

"The GUI could be more intuitive. Also, we'd like streaming telemetry. Zabbix might have this feature, but I haven't seen it yet. It took us a long time to get started because the documentation isn't very descriptive. We had to go through various sources like YouTube and forums to get this solution working."

"It is expensive. They have to look at the model around when we move to cloud and how that's going to work. The licensing cost does pay off because of the improvements in support to our business."

"The pricing is fairly market-related. They have been very lenient because we have been working with them for so long. An example is that we're currently migrating some of our services to AWS, and they've given us a grace period for some of the things to help with the migration and not to grow additional costs while we are migrating, but it's still on par with the market."

"Given our spend and the amount of service we have in it, the pricing is quite reasonable."

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

"I can say it's not that cheap because the licensing is a little bit costly"

"Pricing and licensing is based on the requirements."

"The organization is not just purchasing a license for the product, but also managing services and professional services from ITRS. Another factor is if the implementation is going to be in production, non-production, or both."

"Its price is reasonable. It isn't too expensive, and it isn't too cheap, but it also depends on a company's volume and negotiation."

"I was using the free, Community Edition."

"This solution is open-source and free to use."

"It is free, which allows us to reduce costs."

"Its licensing is fair. It seems to be much cheaper than others."

"There is no license but we need to pay for support."

"It is freeware. We still use the free version of Zabbix."

"We purchased Zabbix for a good price, including support"

"If you have 20,000 hosts, the support costs around €95,000 for a year."