What it is for
This is where you change the error. Everything here changes state, which is why it lives away from the diagnosis screen.
Status
Four states, not twenty: open, investigating,
fixed and ignored. A long list makes each person pick
something different for the same error, and then the column filters nothing.
Marking as fixed asks for the version it was fixed in. That
version is what meulog uses later to detect a regression: if the
same error shows up on a later version, it comes back to the list on its own with
a Regressed badge, and the regressao event fires for
whoever is listening.
Whose fault
The category answers "whose fault is this": ours, the customer's, a third party's, or the environment's. It becomes a facet in the list, and it is what lets you ask "how much of my noise is not mine".
Owner
Who picked the error up. It shows in the list, so nobody investigates the same problem twice.
Silence for a while
A known error that will be fixed in the next release does not need to wake anyone up. Silencing does not delete: occurrences keep counting, the error stays in the list, and only the alert stops. Once the period is over, it starts notifying again on its own.
Merge
Two groups that are the same bug. The merge applies to what already came in and to what comes next: a new occurrence with the source fingerprint writes straight into the destination. You can split it back.
Regroup
When you write a grouping rule, it decides the group on the way in. What was already in the database stays as it was. This button applies today's rules to yesterday's occurrences.
Regrouping only reapplies the screen rules. The other two grouping layers (what the source asked for, and the computation over the stack) cannot be reproduced from what ended up in columns, and recomputing would give a different fingerprint than the original for every error that came in without stack frames. No rule matched, nothing changes.
The dry run comes first: the screen shows how many occurrences would move and where to, and only then offers the button. There is no undo.
Customer-facing text
Writes, with AI, what to tell whoever reported it. It only runs when you ask: it is one model call per click. Nothing is sent; the text shows up on screen for someone to read first.