In this chapter, you learned that it is necessary to collect the monitoring environment data (Zabbix server proxy, database, and GUI) so that we know which performance tuning to do. You also learned that each component has its specific collections. For example, the Zabbix server has internal keys, and the Zabbix database can have your data collected by Dbforbix. We also need to pay attention to monitoring services, applications, and processes that are running to perform monitoring of the rest of the production environment.
In the next (and last) chapter, we will improve your understanding of the extent of monitoring, in addition to the infrastructure. We will try to show that Zabbix can (in my view, should) focus on the monitoring of the entire business and not just the infrastructure. That's the next challenge—meeting all levels of organizational structure:
- Operating system: This plays an important role because it is the basis of all components. It can generate bottlenecks that are often unknown.
- Hardware: This is as important as the operating system. It is the simplest to solve. If the hardware is exhausted, you just have to buy a new one. Often, the hardware is underutilized because the other components are misconfigured.
- Storage: This is directly related to the hardware, operating system, and database engine. It is where data is generated and handled by the application.
All of these components should always be considered when we are thinking of monitoring the health of an environment.
Don't forget that Zabbix doesn't work alone and although very relevant, this is not the only point to note about performance.