We have found similar issue with TrueSight Service CI - incorrect status?
Followed all the steps mentioned and found out below things,
1. We have exctracted baroc for impacted CI and in root_cause slot we have found component ipmacted with CRITICAL severity.
2. Now, when we search event in mcdb with details (as per root_cause slot) we did found one but with SIM_COMPONENT_CHANGE object
Now we are bit confuse how its going. If anyone knows, please explain.
Please help us, so that we can troubleshoot this issue further.
Thanks in advance!
It is resolved now. By calling rule i.e. mc_tool_rule with msend command lead us to see non impacted CI's on TSIM console.