Introduction

Raccoon records what your app does in production: requests, jobs, commands, scheduled tasks, queries, outgoing requests, cache, mail, notifications, logs, exceptions and the users behind them. It groups exceptions into issues, emails you when something breaks or slows down, and keeps 30 days of data.

Laravel apps keep the official laravel/nightwatch package and its agent, and only change where the agent sends. Node.js and Next.js apps use the raccoon-nodejs package. Anything with an OpenTelemetry SDK (Python, Go, Java, Ruby, .NET) can export to Raccoon directly.

How it's organized#

• An organization is your team. It has members, a plan and a monthly event allowance. You can belong to several.
• An application is one codebase, such as your API or your storefront.
• An environment is one place that application runs, such as Production or Staging. Each environment has its own data, its own token for sending events, and a browser key for frontend monitoring.

You switch environments from the menu at the top of the dashboard's sidebar.

Connect your first app#

1. Create an account. Signing up creates your organization.
2. Create an application. The setup screen shows the first environment's token. You can find it later under Settings → Environments.
3. Follow the guide for your stack:
   • Laravel, with the Nightwatch agent.
   • Node.js and Next.js, with raccoon-nodejs.
   • Browser monitoring, for Core Web Vitals and frontend errors.
   • OpenTelemetry, for other languages.

Events show up within about 10 seconds. If they don't, each guide ends with a troubleshooting section.

What to read next#

• Dashboard pages explains what each page shows.
• Issues and Alerts and thresholds cover being told when something goes wrong.
• MCP server lets coding agents such as Claude Code read your production data.