Impact Tree on service is not complete

[Lhora Alvarez]

Hi experts!

The service I am configuring has many CIs connected to it but when I check on the Impact tree, only the entry points are listed.

I tried running the Event Management - Impact Tree Builder Job but it still won't lists all the CIs correctly.

How do I correct the Impact Tree?

[Tushar]

Hi @Lhora Alvarez 

There are a few things you can do to correct the Impact Tree:

1. Make sure that the Event Management - Impact Tree Builder Job is configured correctly. The job should be configured to run on a schedule that is frequent enough to capture all of the changes to the service and its associated CIs.
2. Check the logs for the Event Management - Impact Tree Builder Job to see if there are any errors. If there are errors, you can try to resolve them by modifying the configuration of the job or by troubleshooting the underlying issues.
3. Make sure that the service and its associated CIs are properly classified. The classification of the service and its associated CIs will determine how they are included in the Impact Tree.

Please, don't forget to mark my answer as correct if it solves your issue or mark it as helpful if it is relevant for you!

Regards,
Tushar

[Lhora Alvarez]

What does "properly classified" in #3 mean? Do you mean the dependency of each CIs?

[Lhora Alvarez · Accepted solution]

I figured out what happened. 

The Impact Graph History record for the affected service was accidentally modified. So I manually revert its fields back to its original values.

Now, the Impact Tree is displaying as expected.