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
There is the fault analyzer in Domino which works on collected client and server NSDs providing some, not all information LND had.
LND was an IBM support esset, which was mainly intended for support with support database search integration.
Some of it was helpful for customers and partners.
The most important part to pinpoint problems is the collection of relevant data and providing this data to HCL support or a business partner with special troubleshootign skills.
No tool in the world can replace that. Not even AI .. But it would be worth a try ind training ... (that's a different story).
Filtering the data after "thinking" someone has found the root cause, is one of the biggest issue when trying to troubleshoot a problem as a senior troubleshooter.
IMHO Domino has a lot of great troubleshooting information. Most information is collected for you.
But IMHO the information in NSD and memcheck was never really intended for customers to look into on their own.
It's mainly intended for senior support and development to look into.
I would more focus on collecting the right information and enable the fault analyzer, which helps you to get an idea what the problem could be.
If an admin can't read NSDs without tools, it is quite unlikely the admin (or developer) can do root cause analysis with a tool like LND. I am in the Notes/Domino troubleshooting business since over 20 years and I can tell a tool will not really help you.
Enabling fault recovery and diagnostic collection should be a must for every Domino environment.
Same as not disabling debug ThreadID which is on by default for good reason for troubleshooting.
Some settings will always need to be added like memory trap leaking, semaphore debugging etc.
But with diagnostics (enabled in server documents) admins are well preparated for first crash data capture.
[ Daniel Nashed / https://blog.nashcom.de ]
It will be good if the server crash or malfunctions generate a report for the further reference with out any dependence on any Parameters
currently we have to enable the parameters to and collect data and Waite for the server to crash again . HCL Team will recommend to disable the parameters because it will slow down the server performance
Yes, please
It's not good enough to merely analyze NSDs. Often (very often) the NSD does not contain enough information to determine the cause of the crash or hang or malfunction, especially when these occur seemingly at random. HCL really needs automatic tracing to monitor every dependencies on the platform even before there is a crash, hang or malfunction. We don't lose customers because we can't analyze the NSDs. We lose customers because HCL Support's NSD analysis finds no root cause so the crash, hang or malfunction continues to happen with no plan for remedy. See DDXP-I-1015.
YES YES YES YES YES
This is much needed.
Yes! Please!