All apps will eventually throw errors that will be captured by developers in try/catch blocks and handled accordingly
or sometimes they will occur without being handled.
In the case of errors (i.e. HTTP calls that return 4xx or 5xx status codes), we wrap the call in a try/catch block
for async/await operations or using then and catch for promises and use the pushError API provided by Grafana
JavaScript Agent to report them.
The Faro Errors Instrumentation automatically captures uncaught errors. It is listening to the onerror and
onunhandledrejection, then it parses the events in order to extract the stacktrace and finally they are reported.
The captured errors are stored in Loki.
The errors that are captured server side are reported manually by writing them to a file which is then read by the Grafana Alloy.
The captured errors are stored in Loki.
Given the way how the API reports the errors, they can't be filtered by kind=exception since they will appear as
logs.
- Manually instrumented requests returning an error
- Navigate to the Seed page
- Try to run the seed process at least twice (it won't work second or third time)
- Manually trigger an error
- Navigate to the Features page
- Click the buttons from the
Error Instrumentationcategory
- Capturing a React error
- Navigate to the Features page
- Click the
Incrementbutton from theError Boundarycategory 3 times
- Explore page
- Navigate to the Explore page in Grafana
- Select the
Lokidatasource - To properly view the stacktrace, click on
Escape newlinesin Grafana, above the logs
- Dashboard
- Navigate to the Frontend dashboard in Grafana
- Check the
Exceptionscategory
