Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Dynamic prioritization

Besides status, priority is the second important aspect of a CI. The status of a component indicates the health of a component, but it does not convey how it impacts your business.

Two CIs having the same status can cause very different impacts on your business. For example, an out-of-order printer might have a lower impact on your business than your online shopping web server not responding. Although both CIs might have an UNVAILABLE status, the priority for resolving the two problems will be completely different.

Dynamic prioritization is a system of setting the priority of a component to help you understand what problems to work on first, based on whether a component is in demand at the time (as defined in its service schedule), the severity of its status, and its impacts.

The final priority of a component is determined by comparing the component's self priority and impacts priority. The greater value becomes the final priority value of the component.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*