Finding associated IPs for cloud schedules can cause poor performance and abnormal SQL response time

[srikanthnelapud]

DESCRIPTION

In Paris, we've shipped an enhancement that considers not just Public IP, for Deep Discovery post-Cloud Discovery of Cloud Schedule, but to consider even the Private IPs. Some of the queries are added in the script include - "CloudDiscoveryScheduleConfig".

ISSUE

In the process of adding the changes w.r.t above enhancement, the way the queries are written, the sequence of triggering them, and having no index for object_id column in cmdb_ci._nic table is causing performance issues that are impacting the Shazzam thus leading to poor performance.

Fix:

1. Added the 'object_id" as an index for the "cmdb_ci_nic" table
2. Made changes to the Script Include - "CloudDiscoveryScheduleConfig"

Available OOTB via "PRB1495931" (San Diego)

Related Case(s): CS5334523, CS5271772

[John230]

What were the changes made to the script include?