HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
really, really, really need this functionality. Governments need to keep the logs for x months.
I know the log.nsf/domlog.nsf archive method, but that creates a much bigger issue. This created a huge database. Our domlog.nsf grows several GB per day.
The situation with domlog is even worse. We have configured archiving and storage of records for the last 3 days, but the database cannot be opened, because thousands of records are created every second. To view the data, you need to copy the database to local and open it, which takes 6 or more hours. How can we talk about operative analysis and problem solving?
NSF is not intended for logging. One just need to admit it and give the opportunity to use other special modern bases instead.
I agree. Log.nsf can grow to a point where it has serious performance impact, even with moderate log settings and retention settings, because it cannot be compressed or renamed at runtime.
Currently a server downtime is required to compress it or to delete it/rename it (if for some reason one wants to or has to keep older log entries).
To keep older logs without the log.nsf growing too big. It‘s slow to open sometimes even with the default 7 days retention because it‘s too big.