This article discusses what to do when seeing too many facts in WGS 10 and how to reduce them. You can reduce the number of facts published in 2 ways. There is no impact on viewing the data; only facts not typically needed are removed.
1) On the WGS properties, turn off any publishing for data that are not evaluated in any of your policies. If using the default policies, the following are not needed:
Authinfo, Namelist, Process, Subscriptions, Topics, ModelQ, Client Connection Channels, MQTT Channels
2) If you are running WGS prior to 10.1.1.2, you may see a lot of facts that you do not use in sensors. These can consume a lot of resources and since they are not being used, this adds resources required for processing.
Since queues and channels are the most prevalent objects, you benefit the most from removing unused facts.
Launch your database maintenance tool and switch to the nastel_apmwq schema (or database):
use nastel_apwmq;
Queues:
DELETE FROM WGS_FACT_LIST where obj_type = 2 and attr_value not in (3, 9, 10, 12, 15, 17, 18, 20, 1226, 1227, 2016, 2022, 2029, 3128, 3129, 3130, 3131, 20109);
DELETE FROM WGS_FACT_LIST where obj_type = 3 and attr_value not in (3, 9, 10, 12, 15, 17, 18, 20, 193, 1226, 1227, 2016, 2022, 2029, 3128, 3129, 3130, 3131, 20109);
DELETE FROM WGS_FACT_LIST where obj_type = 4 and attr_value not in (3, 9, 10, 12, 15, 17, 18, 20, 1226, 1227, 2016, 2017, 2018, 2022, 2024, 2029, 3128, 3129, 3130, 3131, 20109);
Channels:
DELETE FROM WGS_FACT_LIST where obj_type = 6 and attr_value not in (234, 1511, 1527, 1528, 1532, 1534, 1535, 1536, 1538, 1539, 3505, 3506, 3528, 3529, 20109);
Listeners:
DELETE FROM WGS_FACT_LIST where obj_type = 17 and attr_value not in (1024, 1522, 1599, 3552, 3556, 3557, 20109);