Configure and deploy flexible business services and monitor the availability of your business and its individual components.
The availability of a business service tends to depend on the state of many interconnected components. Therefore, detecting the current state of a business service requires a sufficiently complex and flexible monitoring logic.
Define flexible business service trees and stay informed about the state of your business services:
- Business services can depend on an unlimited number of underlying components
- Select from multiple business service status propagation rules
- Calculate the business service state based on the weight of the business service components
- Receive alerts whenever your business service is unavailable
Check out the video to learn how to configure business service monitoring.
How to configure business service monitoring:
- Navigate to Services – Services
- Click the Edit button and then click the Create service button
- For this example, we will define an Online store business service
- Name your service and mark the Advanced configuration checkbox
- Click the Add button under the Additional rules
- Set the service status and select the conditions
- For this example, we will set the status to High
- We will use the condition “If weight of child services with Warning status or above is at least 6“
- Set the Status calculation rule to Set status to OK
- Press the Add button
- Press the Add child service button
- For this example, we will define Web server child services
- Provide a child service name and a problem tag
- For our example, we will use node name Equals node # tag
- Mark the Advanced configuration checkbox and assign the service weight
- Press the Add button
- Repeat steps 12 – 17 and add additional child services
- Simulate a problem on your services so the summary weight is >= 6
- Navigate to Services – Services and check the parent service state
Tips and best practices
- Service actions can be defined in the Services → Service actions menu section
- Service root cause problem can be displayed in notifications with the {SERVICE.ROOTCAUSE} macro
- Service status will not be propagated to the parent service if the status propagation rule is set to Ignore this service
- Service-level tags are used to identify a service. Service-level tags are not used to map problems to the service
The post Handy Tips #28: Keeping track of your services with business service monitoring appeared first on Zabbix Blog.
