CMDB Query Builder Insight queries show high memory usage - Known Error

CMDB Query Builder Insight queries show high memory usage Description Insight queries are not shown on the CMDB Query Builder page but they are provided OOB and are run through their corresponding scheduled job so that associated reports can be populated by running those queries in background. No user need to run them and thus can show memory issues even without any user interaction.

A couple of insight queries are shown to have a huge memory footprint.

Steps to Reproduce

Any of the following QB queries show high memory footprint : 1. Insight - Cloud DB Instances 2. Insight - Cloud Applications

Workaround Find out the exact query that is causing the issue, it should be one of the 2 queries mentioned in the STR.

Try the workaround in following order:

Workaround #1 : Try this in sub-prod first because this workaround does not guarantee to avoid the high memory issue but, if worked then could avoid going to Workaround#2. This workaround is to adjust the batch size of the problematic query : a) Navigate to the qb_saved_query table list view b) Open the offending query record c) Change the "Execution Batch Size" to 50, and save.

*IMPORTANT NOTE for Workaround #1*

Changing the batch size to 50 means slower processing at the expense of avoiding memory pressure. That means it'll take more time to process the entire query through multiple batches now that each batch deals with less amount of data. If its taking too much time or is timing out, then gradually increase the batch size in steps of 50

If Workaround #1 did not work then try Workaround #2

Workaround #2 : Deactivate the relevant job corresponding to the problematic QB query (eg. ' Insight - Cloud DB Instances', ' Insight - Cloud Applications' ) with the following steps:

a) Navigate to the sysauto_query_builder table list view b) Search for the record with name of the job which will be same as the name of the query c) Open the record -> Set active=false -> Save the record (you might have to change the scope to make the record editable, its possible to do it on the record itself in the form view, by clicking on the link at the top)

*IMPORTANT NOTE for Workaround #2* Impact of disabling the job: You will not be able to see cloud DB instances data in the "Cloud vs non-cloud resources" chart when "Insight - Cloud DB Instances" scheduled job is disabled. Same applies for 'Insight - Cloud Applications' query.