Yeeted
How it works Agent loop Under the hood Plans Docs Log in Get started

BUILD AND RUN

Logs and metrics

Every service has a full observability page: click any service in the dashboard to open a tabbed view with everything about it in one place.

  • Logs: build output, your app's console, system messages, and a request log of the traffic hitting your service (method, path, status, latency) without adding any instrumentation.
  • Service metrics: CPU, memory, and disk I/O for your deployment, per environment.
  • HTTP traffic: your 2xx/4xx/5xx counts, split into responses your app gave versus responses Yeeted answered for it (like the brief “starting…” page while a preview wakes). When a graph goes red, you can immediately tell whether it's your code or not.
  • Builds: the build history behind the service, newest first.

Your agent can read logs too. Just ask “show me the logs” or “why did that build fail?” and it can pull them to help debug and ship a fix.