![]() ![]() 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |