It would be useful to recognise when a new error report is similar to or represents the same underlying issue as a report that already exists in the database. Users should still be able to see all instances of a submitted error. We could start small, by showing the number of instances for a certain error and link to a list of such instances.
Michael, If you have some ideas on how to implement this feature, please add your notes here since I hear that you are busy with toaster. I might find someone at Wind River to work on it depending on the complexity.
(In reply to comment #1) > Michael, > > If you have some ideas on how to implement this feature, please add your > notes here since I hear that you are busy with toaster. I might find someone > at Wind River to work on it depending on the complexity. Currently I've got this working in a local branch using a Levenshtien distance on a prime error (the first in the database). So the flow goes like this: New data comes in -> Calculate levenshtien distance from the first error in the database -> store that in the record for this error. Then when you wish to find existing similar reports we just query the column for the Levenshtien distance where it's = this report's distance +/- some tolerance value. This means that the lookup is trivial which is the bit that will happen very frequently. The problem I have is that calculating the distance can take seconds to several minutes on standard hardware, as the size of the log being compared varies greatly. This means we wouldn't be able to send immediate feedback on a duplicates/similar errors existing. I'm not sure if that's important or not, I think at some point we're going to have to do a fair bit of computation so it's just a matter of where in the flow that is acceptable.
This feature has now been added and available as of 69ee069a6a49d4ed9a37d22fdb7600d7f1555be2
feature implemented