# Logs and monitoring, built in.

URL: https://antideploy.com/platform/logs-and-monitoring

What your app printed, how many requests it served and how fast, and whether it is running right now. You and your coding agent read the same things, so questions like why is it slow are answered from facts. If an app goes down you get an email, and another when it is back.

## At a glance

- **Logs on demand**: What your app printed, recent lines, newest last
- **Traffic metrics**: Requests, errors and response times for up to 30 days
- **Health about every five minutes**: Healthy, degraded, down or unknown
- **An email when it goes down**: And another when it is back

## Read what happened, before you guess.

When something is slow or broken, logs say what happened and metrics say how often. Your agent can read both without opening a browser.

### Logs, metrics and health in three calls.

Logs are what the running container has printed, newest last. Metrics are requests, server errors and response times over the last days. Health is the last reading of whether the app is running. Your agent reads them when you say the site is slow or failing.

- Logs return 100 lines by default and up to 300 on request
- Metrics cover up to 30 days, and 7 by default
- A project key can read all three for its own application

[See the Agent API](https://antideploy.com/platform/agent-api)

**Your agent runs**

```bash
API=https://antideploy.com/api/v1

# what the running container printed, newest last
curl "$API/logs?applicationId=$APP_ID&limit=100" \
    -H "Authorization: Bearer $TOKEN"

# requests, errors and response times over the last 7 days
curl "$API/metrics?applicationId=$APP_ID&days=7" \
    -H "Authorization: Bearer $TOKEN"

# running or not, and when we last looked
curl "$API/health?applicationId=$APP_ID" \
    -H "Authorization: Bearer $TOKEN"
```

Related: `GET /api/v1/logs`, `GET /api/v1/metrics`, `GET /api/v1/health`

### If it goes down, you hear first.

Antideploy checks every live app about every five minutes. An app counts as down only after two checks in a row, so one bad moment does not turn a badge red or send you an email. You are emailed when an app goes down and again when it is back. Nothing else.

- A crash or running out of memory is reported with the reason, and the logs say what the app was doing
- An app that is asleep is healthy: the next visit starts it
- Deploy failures are emailed separately, with the reason

[See what a failed deploy tells you](https://antideploy.com/platform/deployments)

**What the states mean**

```
healthy    running, or asleep until the next visit
degraded   running again, but it crashed in the last 15 minutes
down       it stopped by itself, on two checks in a row
unknown    we could not check just now
```

## Facts to act on, not charts to admire.

Monitoring here is small on purpose: the few signals that tell you whether to look, and the tools to look.

- **Logs from the running app.** Everything your app prints goes to its logs, and the console's Logs tab and the API read them. Recent lines, newest last.
- **Build logs, when a deploy fails.** A failed deploy keeps the end of its build log and what the app printed while Antideploy tried to start it, beside a sentence that says why it failed.
- **Traffic metrics.** Requests, server errors and their rate, the median and the 95th percentile response time, and requests per day. Requests count everything that reached the app, bots and each asset on a page included, so they are not visitors.
- **Health, checked for you.** Whether the app is running, crashing or out of memory is checked about every five minutes, so the console shows what is true now and not what was true when you deployed.
- **Told when it matters.** An email when an app goes down and another when it recovers, and one when a deploy fails. Not on every check, and no digest.
- **Your agent reads it all.** Logs, metrics, health and deploy history are all in the API, so when you say the site is slow your agent looks at the metrics and the logs before it guesses.

## What each signal tells you.

On every plan, for every app.

| Signal | What it tells you |
| --- | --- |
| Logs | What your app printed: errors, requests, anything you log. Recent lines only. |
| Metrics | How often things happen: requests, server errors and the error rate, median and 95th percentile response times in milliseconds, and requests per day, oldest first. |
| Health | Whether the app is running right now: healthy, degraded, down or unknown, with the time it was last checked. |
| Deploy history | Every deploy, the commit it built and, if it failed, why. |
| Email | When an app goes down, when it recovers, and when a deploy fails. |

## Here's where it stops.

A platform that only tells you what it is good at is one you find the edges of in production. These are monitoring's.

### Health is about running, not pages

The check looks at whether your app is running, crashing or out of memory. It does not load your pages, so a running app that serves errors is something to find in the metrics and the logs.

### A reading, not a live probe

Health is the last reading from a sweep that runs about every five minutes. Compare when it was last checked with when you deployed before you conclude anything.

### Recent lines, not an archive

Logs are what the running container has printed recently. Send them to a service of your own if you need to keep them.

### No CPU or memory charts, and no alert rules

Metrics cover traffic and errors. The only alerts are the down, recovered and deploy-failed emails. If you need more, instrument your app and send the data to a service you control.

## Monitoring questions, answered.

Anything else? Write to us and a person answers.

[support@antideploy.com](mailto:support@antideploy.com)

### How often is my app checked?

About every five minutes. Health is the last reading from that sweep, not a probe taken at the moment you look.

### When do I get an email?

When an app goes down, when it recovers, and when a deploy fails. Not on every check, and there is no digest.

### What does degraded mean?

The app is running again but crashed in the last 15 minutes. A broken app that people keep visiting is started by every visit and crashes again, so it is not counted as recovered until it stays up.

### Does a sleeping app show as down?

No. An app that is asleep is healthy, and the next visit starts it.

### How many log lines can I read?

100 by default and up to 300 in one request. They are the most recent lines the running app printed, newest last.

### What do the metrics count?

Requests, server errors and their rate, median and 95th percentile response times, and requests per day. Requests include bots and every asset on a page, so they are not a count of visitors.

### How far back do the metrics go?

Up to 30 days. The default is the last 7.

### Can my coding agent read logs and metrics?

Yes. Logs, metrics, health and deploy history are all in the API, with an account token or a project key for that application.

### Can I set my own alerts?

Not today. The only alerts are the down, recovered and deploy-failed emails. For anything else, send your own metrics to a service you control.

### Does it cost extra?

No. Logs, metrics, health checks and the emails are in every plan, including Free.

## Everything else your app can use.

Every service is created by your coding agent, wired into your app, and included in the plans. [See the whole platform](https://antideploy.com/platform).

- [Hosting](https://antideploy.com/platform/hosting)
- [Static sites](https://antideploy.com/platform/static-sites)
- [Deployments](https://antideploy.com/platform/deployments)
- [Database](https://antideploy.com/platform/database)
- [Authentication](https://antideploy.com/platform/authentication)
- [File storage](https://antideploy.com/platform/file-storage)
- [Email](https://antideploy.com/platform/email)
- [AI models](https://antideploy.com/platform/ai-models)
- [Cron jobs](https://antideploy.com/platform/cron-jobs)
- [Custom domains](https://antideploy.com/platform/custom-domains)
- [Environment variables](https://antideploy.com/platform/environment-variables)
- [Security checks](https://antideploy.com/platform/security-checks)
- [Console](https://antideploy.com/platform/console)
- [Agent API](https://antideploy.com/platform/agent-api)

Facts on this page were checked against the live platform on 5 October 2026.

## Know before your users do. Deploy something.

Paste the sentence into your agent, click Approve once, and your app is watched from its first deploy.

To set this up, give your coding agent this sentence:

```text
Set this project up to deploy on Antideploy. Fetch https://antideploy.com/agent.md and follow it.
```