Logs
Bool keeps a running log of what your app is doing, so you can see what’s actually happening — useful for spotting a bug, checking that a feature works the way you expect, or just understanding your app’s traffic.
Viewing your logs
Open your project’s Dashboard → Logs. Each row is one request, showing its time, type, HTTP method and path, the user it came from (if your app has its own accounts), the response status, and how long it took (latency).
The Type column names the request in your app’s own terms rather than in
HTTP: a write to your todos table reads as todos Created, a read as
todos Query, a sign-in as Signed in.
You can narrow the feed by:
- Time range — 24 hours, 7 days, or 30 days
- Event type — Entity Created, Entity Updated, Entity Deleted, Entity Query, Auth events, Page views, or System
- Status — success (2xx–3xx), client errors (4xx), or server errors (5xx)
- User — click a row’s user to see only that person’s requests
The feed pages as you scroll back, newest first.
The Logs tab is owner-only — collaborators you’ve invited to a Bool don’t see it, even ones with edit & publish rights.
How it works
Every request your published app makes for data, sign-in, or a page load passes through the Bool gateway — the managed backend layer that sits between your app and its data (the same layer behind Sign-in for your app’s users and Analytics). Because the gateway is the thing actually handling the request rather than code inside your app, it can log each one without your app needing any logging code of its own.
Logs are captured at that raw gateway level, which is why a single page load can produce several rows — one per request the browser actually made.
Availability
Logs come with newer Bool projects automatically — there’s nothing to turn on, and the tab is there whether or not you’ve published yet — the data and sign-in calls your live preview makes are logged too. Page views are only recorded for a published app.
If you don’t see a Logs tab, either you’re not the Bool’s owner, or the project runs Bool’s older backend. In the second case you don’t have to start over: Bool can make an upgraded copy of it — see Upgrading an older app’s backend.