This is just a very brief follow-up to Duncan's last post, which mentions Known Errors but does not define them.
A Known Error is an output from Problem Management (or more accurately, your Problem Resolution process). For a definition of a problem, click here.
If you think of a Problem as being something you don't understand, think of a Known Error as something you do understand – even if you don't know yet how to fix it just yet.
In the case of a software bug, it would be after analysis of source code and algorithms. In the case of an infrastructure problem it is after carefully verifying the conditions necessary for repetition of the Problem and (ideally) identifying the faulty components.
Known Errors typically have two parts. The first of these is the description of the Known Error itself, showing users or product modules and versions affected. The second is the Workaround and/or Change:
- Workaround – a way to bypass the fault you've previous described that can be used by Customers.
- Change – to resolve the underlying Problem.
In practice, many support professionals people seem to raise Known Errors whenever any error condition or bug is proved as repeatable, rather waiting for the Problem to be diagnosed (fully understood). Also, many raise a Known Error even if a Workaround is not currently available – simply to help Incident logging staff.
Known Errors are used during the Incident logging and resolution process, as a source of Workarounds for customers, and as an information resource for Customer-facing Incident handling staff. Because of this, we've made it so that searching Known Errors is quick and painless from Incident logging in Serio Release 5.