How does the Tool work internally?
which collects the report which will than be rsynced into the internal network and be given to a next instance service which then stores the report into a database. Then there is a third service using 2 processes on different hosts involved which tries to find similarities between stacks stored in the database based on the information originally send in the reportmail.xml document, this then groups similar stacks together and assigns one StackMatchID into the database. Here there is some kind of well almost “fuzzy logic” involved in detecting similarity and there can be false positives while doing that and on the other hand also sometimes the same problem root cause might lead to serveral StackMatchIds. Sun developers have an internal (also closed source) web frontend to access the crash report database and some commandline tools are also available to Sun developers. Sun also does some statistical analysis of the data collected in order to find highscorers that need more urgent fixing
