1 of 1 people found this helpful
The Graph Walk Query API is designed to step down the full relationship tree to show all relationships for a CI, therefore as you have changed the level from 2 to 1 then you will see this error.
2 Levels is not very deep i.e. when returning the results in the Explorer, it will only display the CI plus one level down.
If you increase this to say 5, then I would expect you would see longer delays as it will attempt to display 5 levels of CI relationships in the Explorer (0 = no limit).
I would suggest that you keep it at 2 to stop the errors.
Here are some reference documentation for this call:
2 of 2 people found this helpful
Happy to read you again,
I am not totally (a little bit, but not totally) stubborn, so I change the configuration to avoid the issue, but what I don't understand is why my Reconciliation go through the graph? To reconciliate relations maybe, but why 2 levels, only one is enough.
Actually we get too much CI in the explorer, for example for a vCenter, I get more than 400 esx on the first level (and so more than 8000 VM under the ESX), so on some view this waiting time could be a little bit too long.
I will work on that.
I believe this functionality (API query) came in with the Impact Simulation and Impact Modelling functionality, which applications use this to be able to create and consume the records that are used in the Service Modelling for alarm management.
I guess BMC have tied the levels into one setting for all the application using the QC.