What is the usefulness of mongo table license_stats?
When I go to database "len" I can see that table "license_stats" is now 700mb uncompressed. I opened it and didn't find any useful information in there.
My main question is how is this table maintained? Is there any mechanism for regularly purging of the data?
Thanks in advance
- Community Thread
- Forum Thread
- RSA NetWitness
- RSA NetWitness Platform
- sa server
It is used by licensing and also live feedback (to monitor the license usage). Is this a internal system or customer environment you are seeing 700mb uncompressed. And any additional insight will also help, what you are looking for ?
Thanks for the information. I'm interested to know how is this table maintained as it grows. Is there a mechanism in place to delete the oldest entries and keep the table to a manageable size (for this particular system with the RSA's implementation of mongo)?
As far as I know, no mongo table except the ones for ESA & IM alerts have a facility for "maintenance", therefore tables grow (which is transparent to the user) until the system becomes unusable.
I am being proactive and trying to understand if this table is one that the user should keep clean to ensure the good operation of SA server, rabbitmq and tokumx. While I understand that 700mb might still be a bit low, I would assume that no testing has been done to know the impact should this table grew to 2 or 5gb.
Good points and pointers.
Can you share, 700 MB of uncompressed data are you seeing in internal system or in customer environment ?
If I recall correctly, we did performance testing in 10.6.x and figured out that the entries due to license are not large enough over a period of time, to cause any concern which you have mentioned. I have asked Engineering to comment on it too in case anything needs to be accounted or any clean up needs to be done and will revert back or ask the Engineers to update the thread.
In case of ESA & IM the clean up is required because I have seen the DB growing up and resulting in slowing down the system.
Thanks for the info.
It is not just ESA and IM databases that can make the system unusable. A month ago I was dealing with the ESM table causing the sms, im, rabbitmq, h&w to collapse as a result of RSA enabling a Beta feature by default: Admin->Event Sources->Settings.
Even if there is no maintenance mechanism in place, I would be interested to know of any potential impact if I purged the contents of the mentioned table.