First, you should look up "Fault Analyzer" in the Domino 7 Administrator Help for documentation on how to configure this.
I was not aware that there was a specific Fault Reports database until I saw Susan Bulloch's blog about it. After reading that, I configured that database along with all of my Desktop Settings documents. I am housing this database on my 7.0 Cluster server. Before starting the Fault Analyzer task (via a configuration document), the database was pretty useful for storing all of those pesky NSD files.
But this morning I configured the Fault Analysis task. It automatically started shortly after enabling it in the configuration document. The task name is FAULTANALY (which, by the way, does NOT appear anywhere in the Admin Help file...). From one of the comments at Susan's site, you should check out the "Fault Analyzed" , "By Callstack", and "By Occurrences" views. As you can see from the images below, the Fault Analysis does a good job at keeping the data organized.
Fault Reports by Call Stack
Below, note the "Similar fault for.... 43%". In the image there is not one visible, but it also includes "Exact fault for...".
Fault Reports by Occurrence
Below, note the portion of the call stack at the top followed by an Administrative Section. In here, you can add an SPR or PMR numbers to keep track of calls to Lotus Support about these faults. Also, the twistie will show the unique number of clients affected and each of those will have a detail number of how many times each client has had the crash.
Detailed Fault Report
2 comments:
Chris,
Did you find any lotus documentation on the Fault analyzer? One thing that stand out is the "diagnostic pattern file" on the configurations document. Can you download the pattern file?
According to the help file, here is what you should enter for the "diagnostic pattern file":
Enter a file name pattern that Domino will search for. If the pattern is located and it is listed in the file, DIAGINDEX.NBF, the file will be attached to the message that is sent to the mail-in database. DIAGINDEX.NBF contains all of the files associated with the crashing instance of the client or server. For example, the following is a file pattern: addin_log*.txt. These files would be located based on that pattern:addin_log1.txt, addin_log_2004_11_23@16_21_20.txt, etc...
I have not determined how to view the contents of the DIAGINDEX.NBF file, though. It contains any current diagnostics or logging information and console.log. I suppose that if you use that pattern that it would include that file with the report sent to the Fault Reports database.
Post a Comment