We have observed that the QOS_IPC_SHARED_MEMORY_SEGMENTS_UTILIZATION is showing up on a few devices.
<hostname1>.abc.example.net
<hostname2>.abc.example.net
<hostname3>.abc.example.net
We have removed the qos from the S_QOS_DATA and S_QOS_SNAPSHOT and RN, and HN tables in the database.
Yet we see the entries coming up again.
Fix provided and attached to this KB Article.
The updated build resolved the problem with the QOS not being disabled via MCS.
The new/updated template must be deployed to the Primary hub.
It has been confirmed by the customer that the issue was resolved with the test build (new processes MCS template) provided.
To test the results:
Deploy the Setup processes (Enhanced) and enable the shared memory segments utilization qos.
Disable all other qos.
is still present or deleted. It should get deleted.
Configured/selected Shared Memory Segments Utilization in the processes probe.
(QOS_IPC_SHARED_MEMORY_SEGMENTS_UTILIZATION)
Collected some qos.
Deselected /unchecked Publish QOS for Shared Memory Segments Utilization in the IM GUI after 10 or so rows were populated in the relevant RN table.
Double-checked the setting via Raw Configure.
It was disabled as expected.
Run the queries below to check to make sure the QOS was no longer being collected.
select * from s_qos_data
--Run a select to see if the QOS data object is still in the s_qos_data table
select * from S_QOS_DATA where qos like '%ipc_shared_memory%'
--Note the RN table and the table_id
-- run a query to select the data from the table using the relevant table_id
select * from RN_QOS_DATA_0041 where table_id = '135'
This confirmed that the QOS data was NO longer being collected.