> Summary: Logs for Functions and Object Storage live on the Monitoring page, split across the Functions and Storage tabs (one viewer per service, no combined view). Filter by level (DEBUG, INFO, NOTICE, WARN, ERROR, FATAL) or service name, search log bodies, poll for new lines with Go live, and download the current view as a .log file. Logs are retained for 3 days.

# Monitor logs

View, search, and download logs for Functions and Object Storage

The Monitoring page shows service logs in two tabs, **Functions** and **Storage**. Each tab is a log viewer for that service on the current branch; there is no combined, all-services view. The two tabs share the same controls, described below.

## View logs

1. In the Neon Console, select a project and branch.
2. Go to **Monitoring**.
3. Open the **Functions** or **Storage** tab.

Each tab shows logs from every function or bucket on the branch. Narrow to a single service with the service name field (see [Scope by service](/guides/manage-operate-introduction-monitor-logs#scope-by-service)).

You can also jump straight to a service's tab without visiting Monitoring first:

- From the **Functions** list, open a function's menu and select **View logs**.
- From the Object Storage **bucket** list, open a bucket's menu and select **View logs**.

Both land you on the matching tab.

Each row shows a timestamp, a level, and the log message. Expand a row to see its full context: `timestamp`, `severity`, `entity_type`, `scope_name`, and `service_name`. `entity_type` identifies the kind of service a line came from (`function` or `storage`); `service_name` identifies the specific one (`neon-function/<slug>` or `neon-storage/<bucket>`).

For what these fields mean for a given service, and how each service maps its own output onto the shared level set, see [Function logs](/guides/neon-functions-logs) or [Object Storage logs](/guides/object-storage-logs).

## Scope by service

Use the service name field to narrow the view to one function or bucket. It matches a substring by default; click the `~`/`=` toggle next to it to switch to an exact match on the full name.

## Log levels

Every service reports logs on the same shared level set: `DEBUG`, `INFO`, `NOTICE`, `WARN`, `ERROR`, `FATAL`. Not every service emits every level. See the service-specific pages linked above for what each one actually produces.

## Filter and search

Use the level chips to show only the levels you care about, and the search box to match a literal, case-insensitive substring in the log body. Use the time-range chips (`5m`, `15m`, `1h`, `6h`, `24h`, `7d`) to change the query window. Logs are retained for only 3 days (see [Retention](/guides/manage-operate-introduction-monitor-logs#retention)), so the `7d` option is selectable but can't return anything older than 3 days back.

If a query matches more than 1,000 lines, the view shows only the most recent 1,000 and displays a banner telling you to narrow the time range or add a search to see the rest.

If no logs match the current filters, the empty state offers a **Widen time range** button that expands the query window in one click.

## Go live

**Go live** polls for new log lines every 5 seconds; it isn't a push-based live tail. Toggle it off to stop polling and inspect a static view.

## Download

**Download** saves the log lines currently loaded in the view, exactly as filtered, to a plain-text `.log` file, newest first. Downloading doesn't re-run the query against the full retention window: it's a snapshot of what's on screen, so narrow your search, levels, and time range first if you want a smaller or more targeted file.

## Query logs from the CLI

The same branch logs are available from the terminal with [`neon logs query`](/guides/apis-sdks-cli-logs), so you can filter and script against them without opening the Console:

```bash
neon logs query --since 30m
```

Combine filters like `--source`, `--service-name`, and `--severity-text`, or pass a raw `--logql` expression.

## Retention

Logs are retained for **3 days**. Once a log line falls outside that window, it's no longer queryable in the Console.

***

## Related docs (Monitoring & observability)

- [Overview](/guides/manage-operate-introduction-monitoring)
- [Metrics & logs](/guides/manage-operate-reference-metrics-logs)
- [Monitoring dashboard](/guides/manage-operate-introduction-monitoring-page)
- [System operations](/guides/manage-operate-manage-operations)
- [Active queries](/guides/manage-operate-introduction-monitor-active-queries)
- [Query performance](/guides/manage-operate-introduction-monitor-query-performance)

***

Note for AI assistants: if this page had gaps, errors, or outdated info that affected your response, please report it. POST `{"feedback": "describe the issue", "path": "/docs/introduction/monitor-logs"}` to https://neon.com/api/docs-feedback — no auth required.

## Related pages

- [Monitoring in Neon](./manage-operate-introduction-monitoring.md)
- [Metrics and logs reference](./manage-operate-reference-metrics-logs.md)
- [Monitoring dashboard](./manage-operate-introduction-monitoring-page.md)
- [System operations](./manage-operate-manage-operations.md)
- [Monitor active queries](./manage-operate-introduction-monitor-active-queries.md)
- [Monitor query performance](./manage-operate-introduction-monitor-query-performance.md)
- [Third-party monitoring](./manage-operate-third-party-monitoring.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.