IT monitoring solutions have, in my opinion, entered a 'Red Queen Game' phase of evolution. In terms of raw features there very little to choose between them. I will do my best to remain neutral.įor me, both are flexible, highly configurable, stable solutions with a solid history and reputation. Currently, we are developing modules to add features to Zabbix, but they should also work on these features.ĭisclaimer: Following 2+ decades of working with big-vendor IT Ops Mgmt Software - including being technical consultant employed by a global ITOM vendor - I have formed a business focussed on Zabbix. These are the security features and concerns that we have to deal with. 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. For example, when dockerization is going on, how can we check the logs inside the Dockers. We are currently bringing enhancements at our end for different use cases. The market is growing a lot, and it should be enhanced for a lot more things. There should be information about how to reduce the load on the MySQL database, which is what Zabbix is using. When the network is growing, the number of transactions becomes very high, and the database gets overloaded. Sometimes, when you are using the database, it can get overloaded. 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.
A lot of articles are available, but they need to be in proper documentation. We need more scalability features and documentation for different use cases. It becomes complex when we are growing and need to add proxies. I can handle it, but others should also be able to handle it in a better way. Its UI needs to be improved a little bit more so that an end-user is also able to handle it. That said, the issue there is you need the developer to do that if you decide to go that route. In the other end, we are using the API to do that now. Reporting is even, in a lot of ways, missing.
It's probably not the reporting most operations need especially if you need more data for importing Excel or whatever. Reporting in Zabbix means you create a dashboard and then you can schedule that and you get it as a PDF. It is there, however, it's not a real reporting from my perspective. A lot of the time, in that case, we are opening a few tickets for one problem, and then the correlation functionality is very, very limited. From day one, we're using the API to create tickets for our operations, however, the correlation is not good, not there.
There is room for improvement, due to the fact that this first step looks nice, yet it can be improved here for a better combination with the services and the dashboard. The service module started with version six.
0 kommentar(er)
