Documentation
Logsitter watches your Vercel logs and sends a Slack alert the moment something errors. There is no SDK to install and no code to change. This guide covers connecting a project, choosing where alerts go, and tuning what counts as an alert.
1. Connect a Vercel project
Sign in with your Vercel account, then choose a project from the dropdown on your dashboard. Logsitter creates the Vercel log drain for you automatically and begins watching that project's runtime, edge, and build logs in real time.
Prefer to set it up by hand? Each project also shows a drain URL and a signing secret you can paste into your Vercel project under Settings, then Log Drains, using the JSON format.
2. Add alert channels
Create a Slack incoming webhook for the channel you want alerts in, paste the URL into the project, and send a test alert to confirm it works. Slack alerts are free and unlimited. Email delivery is available on the Pro plan.
3. Tune your alert rules
Each project has rules that control what gets sent:
- Minimum severity (warning, error, or fatal).
- Which log sources to watch (functions, edge, build, and more).
- Paths to ignore, such as health checks, with wildcard support.
- How often to re-notify while an issue is still happening.
How alerts work
Logsitter fingerprints every error and groups repeats into a single issue, so a crash loop becomes one alert with an occurrence count rather than thousands of messages. It infers real severity from status codes and output, so a function that crashes with no response is treated as fatal even if the log line was labeled info. Every issue links back to the original log in Vercel.
What we store
Logsitter does not store your raw logs. It reads them from Vercel and keeps only a fingerprint of each issue plus a small amount of metadata. See our Privacy Policy for details.
Need help?
Visit our support page or email support@logsitter.com.