Modal apps, functions and queues in the context graph
Connect a Modal workspace and its apps, functions, sandboxes, volumes and queues join the context graph, with checks on error logs, spend and queue depth.
What changed
Connect Modal with a token ID and secret, and every environment in the workspace joins the context graph: apps, functions and their web endpoints, classes, images, running sandboxes, volumes and queues, synced every 15 minutes. When a sync finds a new version of an app, Polylane records a deployment with the version and who deployed it.
A repository is linked to the Modal app its CI deploys with
modal deploy, and Cloudflare DNS records that point at a
.modal.run endpoint resolve to the function behind it.
Checks
Workspace checks watch stderr log lines across recently active apps, metered spend per hour, the p90 time from creating a sandbox to its container starting, and the number of items waiting in your queues. Each app also gets its own monitor for stderr lines and hourly spend, compared with its usual level.
In investigations
Agents describe an app with its state, deploy history and functions, and read its logs, deployments, sandboxes and spend. See the Modal integration.
Why it matters
Modal functions often fail quietly: a traceback in stderr, a queue that stops draining, spend that climbs. Polylane watches those series and links each app to the repository that deploys it, so an investigation can reach the change behind a failure.
How to use it
- In
Modal, go to Settings → Tokens and click New token.
- Copy the token ID, which starts with
ak-, and the token secret, which starts withas-. - Paste both into Polylane. It checks the pair and starts the first sync.
Modal has no read-only token, so the token carries the permissions of the account that created it. Polylane has no tools that change
Modal.