Logs and metrics
See what your app prints, which requests it gets and how it performs.
Logs
The project's Logs page shows everything your instances write to stdout and stderr. There's nothing to install.
Structured lines get split into fields. That works for JSON objects and for key=value lines. level or severity becomes the severity, message or msg the message, and every other field becomes an attribute you can filter by. For plain text lines, Teral guesses the severity from the text, so a stack trace shows up as an error.
{ "level": "warn", "message": "payment retry", "order_id": "ord_123", "attempt": 2 }Filter by severity, app, deployment, environment, region, instance, text and time. You can also type a question such as "errors in production in the last hour", and Teral turns it into filters.
Requests
The project's Requests page lists the requests the gateway handled, with status, method, host, path, region and duration. Open a request to see how its time splits between the gateway and your app, and which deployment answered.
Headers and bodies only show up for requests matched by a Logging policy.
Filter by status, method, path, app, deployment, environment and time, or type a question such as "404s in the last hour".
Metrics
A deployment's page shows requests per second, latency, CPU and memory across all its instances.
The deployment's Network view shows each instance. Select one to see its CPU, memory, disk and network traffic over the last 15 minutes up to 30 days.
Retention
How long logs are kept depends on your plan. See Settings → Limits in your workspace.