We want to know how many times people encounter errors when they are using the Bridge. Based on this we want to see which error cases we potentially want to make less likely to happen or handle with better (e.g. more specific) error messages.
- all errors are tracked
- a graph exists that shows the amount for each of the different error types over time
From the tech discussion
- we'll add tracking into the root store
- we discussed to implement this through a subscription to the addApplicationErrors mutation so we don't miss any additions no matter how the change of value came together (action/mutation)
- the ErrorUnknown and ErrorSaving will keep their calls to the tracking actions for truly "unhandled errors" (so we will be able to visualize those without having to maintain a list to excludes in grafana)