My q_qos_processor_qos_message.sds file is 32GB in size, what does this mean (apart from a dead NMS server)?
Doesn't necessarily mean NMS itself is dead. It's not unheard of that qos_processor probe stops processing messages in the queue.
qos_processor handles qos enrichment and keeps origin fields up to date in case of changes in robot origin. These days it also handles baselining stuff in the database.
In my prod (6.5) I don't do any of that qos enrichment and I have disabled this due to stability issues.
You could look at tuning message-receiver-bulk-size as well. Default value is 60, so it might help increasing it to something™.Also, increasing enricher threads might help: monitor-enricher-thread-count or monitor-db-updater-thread-count.
Note that I don't necessarily know the impact of tuning these things.
We've also disabled qos_processor since it's garbage.
Retrieving data ...