What it is for
The same data, sliced by where in the code it breaks. One row per unit and method, with how many occurrences, how many distinct errors and how many customers each point in the code produced.
This is the screen for whoever is going to prioritize refactoring: ten different errors coming out of the same file say more about where to invest than ten files with one error each.
Where "where it breaks" comes from
- From the bug report parser, when the format already carries unit and method (madExcept does).
- From the top of the stack, when the event arrives through an API: meulog picks the first frame that is not library code.
The chosen frame is the first one marked in_app, or the first that
does not look like a library. Without that, every front-end error would point
inside React and every Ruby error inside Rails.
"Unit" is what a code file is called in Delphi. Here it can be a Ruby file, a Python module or a Java class: that is why the label on screen reads Where it breaks and not Unit.