# LaraBug > Error tracking for Laravel and JavaScript applications: exceptions, slow requests, queries, queues, scheduled tasks and dependency vulnerabilities, each with the request context behind it. Every page below is linked as markdown. Drop the `.md` for the page a person reads, or ask the page itself for `Accept: text/markdown`. ## General - [Getting started](https://v4.larabug.com/docs/general/welcome.md): These pages cover the two clients, what each kind of telemetry records, what opens an issue, and the integrations. - [How LaraBug works](https://v4.larabug.com/docs/general/how-larabug-works.md): Four words do most of the work in the rest of the documentation. - [Applications and keys](https://v4.larabug.com/docs/general/projects-and-keys.md): Sign in, open Applications, and add one. ## Laravel - [Installation](https://v4.larabug.com/docs/laravel/installation.md): Version 4 of larabug/larabug needs PHP 8.2 and Laravel 11, 12 or 13. - [Configuration](https://v4.larabug.com/docs/laravel/configuration.md): Everything lives in config/larabug.php. - [User context](https://v4.larabug.com/docs/laravel/user-context.md): An exception is easier to fix when you know who hit it. - [Testing your setup](https://v4.larabug.com/docs/laravel/testing.md): Finding out that reporting is broken when you need a report is the wrong time to find out. - [Troubleshooting](https://v4.larabug.com/docs/laravel/troubleshooting.md): Nearly everything is one of the first four. ## Issues - [Overview](https://v4.larabug.com/docs/issues/overview.md): An issue is one problem in your application, with every time it happened behind it. - [Exceptions](https://v4.larabug.com/docs/issues/exceptions.md): An exception event is one time something threw. - [Dependencies](https://v4.larabug.com/docs/issues/dependencies.md): The client reads your composer.lock, compares it against the advisory database, and reports the packages with a known vulnerability. ## Telemetry - [Overview](https://v4.larabug.com/docs/telemetry/overview.md): An event is one thing your application reported. - [Requests](https://v4.larabug.com/docs/telemetry/requests.md): A request event is one trip through your application: the route, the status, the time it took and where the time went. - [Queries](https://v4.larabug.com/docs/telemetry/queries.md): Every statement a recorded request ran, with the time it took and where in the request it ran. - [Queue jobs](https://v4.larabug.com/docs/telemetry/queue-jobs.md): The client reports queue work as well as exceptions, which is what fills the queue pages in the panel: what is waiting, what is running, what failed, and how long a job takes. - [Scheduled tasks](https://v4.larabug.com/docs/telemetry/scheduled-tasks.md): A scheduled task event is one run of one entry in your schedule: what ran, how long it took, and how it ended. - [Commands](https://v4.larabug.com/docs/telemetry/commands.md): An Artisan command that ran: which one, with which arguments, how long it took and what it exited with. - [Logs](https://v4.larabug.com/docs/telemetry/logs.md): Your application's log records, in the panel, beside the exceptions and requests they belong to. - [Mail and notifications](https://v4.larabug.com/docs/telemetry/mail-and-notifications.md): What your application sent, from inside the request that sent it. - [Cache](https://v4.larabug.com/docs/telemetry/cache.md): Every cache operation a recorded request performed: what it asked for, whether it was there, and what it wrote. ## JavaScript - [Installation](https://v4.larabug.com/docs/javascript/installation.md): There is a package per stack. - [Vanilla JavaScript](https://v4.larabug.com/docs/javascript/vanilla-javascript.md): @larabug/browser is the client every other package is built on. - [React](https://v4.larabug.com/docs/javascript/react.md): @larabug/react is the browser client plus an error boundary and three hooks. - [Vue 3](https://v4.larabug.com/docs/javascript/vue-3.md): @larabug/vue is the browser client plus a plugin and four composables. - [Inertia](https://v4.larabug.com/docs/javascript/inertia.md): @larabug/inertia sits alongside @larabug/vue or @larabug/react and adds what Inertia knows: which page you were on, which visit failed, and the Laravel context behind it. - [Source maps](https://v4.larabug.com/docs/javascript/source-maps.md): A minified stack trace says a.b is not a function at app-D4wpJuT4.js:1:48213. ## Guides - [Filtering sensitive data](https://v4.larabug.com/docs/guides/filtering-sensitive-data.md): An error report is a snapshot of a moment in your application, and moments in applications contain passwords, tokens and people. - [Alerts and notifications](https://v4.larabug.com/docs/guides/alerts-and-notifications.md): A tracker nobody reads is a log file with a nicer font. ## Integrations - [MCP server](https://v4.larabug.com/docs/integrations/mcp-server.md): LaraBug speaks MCP, so an assistant that supports it can read your issues while you are working on them. - [HTTP API](https://v4.larabug.com/docs/integrations/http-api.md): Two different things live under /api, and it is worth knowing which one you want. ## Endpoints - [HTTP API](https://v4.larabug.com/api): every endpoint, what it returns, and how to authenticate, as JSON. - [MCP server](https://v4.larabug.com/mcp): streamable HTTP, OAuth. `claude mcp add --transport http larabug https://v4.larabug.com/mcp` - [Reporting](https://v4.larabug.com/api/log): where the clients post events, authenticated with the login key and a project key. ## Optional - [llms-full.txt](https://v4.larabug.com/llms-full.txt): every page above, in full, in one file.