Using the dashboard
How to read and act on what BugWatch has collected. The pages under Install an SDK and Mobile cover getting data in; these cover working with it once it is there.
| Page | Answers |
|---|---|
| Projects | What a project is, when to create a new one, how environments work |
| Project members | Who can see and act on the data |
| Issues | How errors are grouped, how to triage them, how to read a stack trace |
| Logs | Live tail vs search, sending logs, correlating them with errors |
| Releases | Crash-free rate and whether a version is stable |
| Alerts | Rule types, scoping, evaluation, incidents |
| Insights | Volume, error rate, peaks and the issues driving them |
| Traces | Following one request across services, and reading a span timeline |
| Metrics | Time series, labels and cardinality |
| Service map | Which services call which, derived from traces |
| SLOs | Objectives and error budgets |
| Project settings | Keys, environments, deletion |
Two related pages live elsewhere because they are CI concerns rather than dashboard ones: Source Maps & Symbols for making production stack traces readable, and Deployments (CI/CD) for correlating error spikes with what you shipped.