Child downtime is based on the downtime of leaf children, which are defined as one of the following:
Children with no children of their own (such as the end of a branch of the hierarchy tree)
The lowest level specified during configuration of the report in the portlet
The lowest level specified in the SLA definition itself
The leaf children of an element include both children in the hierarchal structure and children that contribute to the state of the parent element. For example, a parent has two children and the second child has two children of its own. From the perspective of the parent, the hierarchy looks like this:
When the SLA Status Report is configured, the level of children contributing to the data calculations is set at 3. Therefore, the parent availability is based on the availability of Child 1, Grandchild A, and Grandchild B. The availability of Child 2 is based on the availability of Grandchild A and Grandchild B. In addition to availability, the report shows the percent of outages and the percent of downtime that each leaf element contributed to its parent. Grandchild A and Grandchild B contributes to Child 2. Child 2 and Child 1 contributes to the Parent.
Child downtime is available in the SLA Status Report. This report can show daily details for today and yesterday, this month and last month, this quarter and last quarter, and monthly for this year and last year. It displays the following:
Typically when calculating the number of outages for a service, all the outages of the children are considered only in terms of their functional impact on the parent. When considering the impact of leaf children on a parent, the outage of each leaf child contributes directly to the number of outages for the parent.
Outages can be calculated based on one of the following:
Element outages
Outage duration and threshold
A change in condition is considered an outage if both the minimum outage duration and the outage threshold condition are met. The minimum outage duration is the number of seconds that the element must be at the outage threshold condition for it to be considered an outage. The outage threshold condition is the condition that the element must reach to be calculated as part of the outage. For example, if the duration of an incident is 10 seconds and the threshold condition selected is Critical, then the element must have a condition of Critical for a minimum of 10 seconds for it to have an outage.
Expressed as a percent, outages contributed are the number of outages that the leaf child had that impacted the parent element in comparison to the total number of outages for the parent. It is expressed as a percent. For example, if a parent had 100 outages and a child had 10 outages, then the outages contributed for the child is 10 percent.
When downtime is calculated for an element based on impact to that element, only those outages on child elements that impacted the service for the element are considered. When downtime is calculated for an element based on its leaf children, all the downtime for each leaf child is factored into the downtime for the parent. Downtime can be shown in seconds, minutes, days, weeks, months, or years.
Expressed as a percentage, downtime contributed is the amount of downtime that a leaf child had that impacted the parent element in comparison to the total amount of downtime for the parent. It is expressed as a percent. For example, a parent has 10 hours of downtime and a child had 1 hour of downtime, then the downtime contributed by the child is 10 percent.
To calculate the committed time of a parent based on its leaf children, the committed time of each leaf child is cumulative. For example, if a service has two servers that are leaf children and each server has a committed time of 7 days a week, then the service has a committed time of 14 days per week.
Availability is the amount of uptime in comparison to the committed time and is expressed as a percent. Uptime is the amount of committed time minus the amount of child downtime.