If you notice that the MongoDb/Data folder (C:\Program Files\\Micro Focus\SBM\Common\Diagnostics\MongoDb\data) is growing too much or too fast, this document should help. Also, the "Collect Logs" feature in Configurator includes the MongoDB database. If the Collect Logs file is too large, you can follow the steps in this document to control the size.
The " mongoDB _winservice. log " files being created in the "SBM\Common\Diagnostics\ MongoDb \ log " directory for Active Diagnostics are not cleaned up automatically. You will need to manually clean them up occasionally.
Active diagnostics using large amounts of CPU and the mongoDB_winservice.log is very large. Emptying the logs can temporarily resolve this. See resolution below.
This is likely the result of the SBM Active Diagnostics Service (pre 10.1.5) or SBM Logging Services (10.1.5 and later) being turned off. The above error messages are generated in the server.log every hour (and in multiples) as a result which is by design and cannot be switched off or avoided.
Mongo DB (also known as Active Diagnostics or SBM Logging Services) is reported by some security tools as a problem on its port 27017 SBM only uses Mongo DB to log information and diagnostics for Support and R&D use.
If you turn up the level of logging to Debug or Trace, it keeps track of a lot of information. With no upper limit set this amount can grow over time. After a few months of logging with no limit set it can consume a dangerous amount of resources.
1. Stop the SBM Logging Services. 3. Copy the default MongoDb files from Program Files\Serena\SBM\Common\Diagnostics\ MongoDb \init\db 5. Restart the SBM Logging Services.
To re-initialize the database, follow these steps: Stop Active Diagnostics (SBM Logging Services) in Configurator. Delete all files in C:\Program Files\Serena\SBM\Common\Diagnostics\MongoDb\data
