Browse all guides
All guides
Docs

Monitoring and analytics

What the Monitoring & Telemetry card shows about your app, and how to record the actions that matter.

DeploymentIntegrations Updated 2026-10-16

Your app's page in the Desk carries a Monitoring & Telemetry card, and it is where you see what the app is doing: how many people opened it, what they did, how the app's functions are performing, and how much it is holding. None of it identifies a visitor.

Views are counted for you

Every app counts how many times it is opened and when it was last opened. You do not add anything for this. The card's App views tile shows the total, with the last visit underneath.

Record the actions that matter

Ask the builder in the chat to record an event where something important happens. For example:

  • "Track an event called signup when someone creates an account."
  • "Track an event called booking_confirmed with the number of guests."

The builder adds the event to the app. Each event has a short lowercase name, up to 64 characters, and can carry a small set of extra details, such as a plan name or an amount. Keep those details small — under about 2 KB per event. An app can use up to 200 different event names.

What the card shows

  • App views — the total, and when the app was last opened.
  • Handle calls — how many times the app's functions ran, the average time they took, and the share that failed.
  • AI images — how many pictures were made, and how many failed.
  • Data records — how many records the app has saved, and across how many collections.
  • Assets — how many files the app holds, and their total size.
  • In-App Events (30 days) — a chart of the five most-used event names over the last 30 days, with a bar for each day.
  • Subsystems & Schema — a summary of the app's functions and saved data: functions defined, their errors and total running time, when one last ran, and the collections with their record counts.
  • Recent Invocation Activity — the latest calls, each marked as a function or an image, with a tick or a cross, how long it took, and how long ago. Point at a failed call to see the reason the platform recorded for it.
  • Build and session health, shown at the top — Active Session or Idle Workspace, Auto-healing progress while a build is repairing itself, and Build failing when it is not.

Events are kept for 90 days and then removed automatically, so the chart always covers a recent window rather than all of history. The details attached to an event are recorded, but the chart shows only event names and daily counts.

The payments block

Once your app is approved to accept money, the card also carries a Payments block. It shows today's revenue, lifetime revenue, the total refunded, the payments still pending or settling, and a list of recent payments with their amounts and status.

The deeper view

Select Full monitoring in session at the top of the card to open the Monitoring panel, which is also reachable as Settings → Monitoring. It repeats the summary tiles and adds detail:

  • Defined Handle Functions — a table of the app's functions with each one's calls, average time, and errors.
  • Database Collections — a table of the app's collections with each one's record count.
  • Recent Invocation Activity — a longer log you can filter to everything, functions only, or images only, showing each call's status, how long it took, and when it ran. Hovering a failed call shows why it failed, in the words the picture or function service used.
  • In-app events — the same 30-day chart of the app's event names that the card shows, so the events you record sit with everything else the app is doing.

What monitoring does not do

  • It does not identify visitors. Events are stored without names, email addresses, or account details. Keep identifying information out of the details you attach to an event.
  • It does not record screens or movements around the app by itself. Only the events you ask for are stored.
  • It is not a separate dashboard. The same events reach the Monitoring panel inside a session (Settings → Monitoring), which shows the in-app event chart at the bottom, below the app's operational health.

Where to go next

To see how many people your app is reaching, Share your app and send the link. For deeper numbers, ask the builder to record an event at each step you care about.