Another way to meet the business areas of our company is to create an SLA tree so that services can be monitored by considering the link with the other monitored layers (operational and tactical).

Usually, an isolated trigger doesn't serve to represent the service and all of its environmental dependencies. It is something like this: a service to the user depends on certain infrastructure components, and these dependencies need to be represented in the SLA reports. Its format is like a tree, where we have the root, trunk, branches, and leaves, and they will be represented by triggers.

SLA reports in Zabbix are—in some environments—in the background, and Zabbix administrators end up not using this resource. But it is important to bear in mind that this feature is one that helps us leverage Zabbix within our company, because it can establish a not-so-technical vision and is more focused on the business.

The important thing is to try to make up at SLA report, not the infrastructure, but the relationship of the user with the service infrastructure. An appropriate structure of SLA tree would look like this:

This approach will give us a consolidated and detailed view of the state of services that are operating in the environment.

This functionality is one of the most important for supporting Zabbix in our company. With SLA reports, we can confront facts and data with the perception of internal or external users. It is also of great value for IT teams when you highlight the availability of services for users.

To learn more about creating your tree services in Zabbix, visit the main page of this topic at https://www.zabbix.com/documentation/2.4/manual/it_services.