Skip to main content
Logs is where you check what your backend did and when. Each entry records one event, such as a GraphQL request that reached your project. Open it from Backend → Logs. The page shows logs for the current project and the environment selected in the Backend Console, for example master. It never shows logs from other projects.

​
Sources

Logs cover two kinds of activity:
  • Core GraphQL — requests that reach your project’s GraphQL API.
  • Custom Function — output from your custom functions.
The Source filter also lists Workloads, Integration, Custom API, and File. See Filter by level, source, and time.

​
The Logs screen

The Logs page showing Requests, Error rate, and p95 latency cards above a table of log entries The page has four areas:
  • Actions — Live tail, a Comfortable / Compact density toggle, Refresh, Export, and Log settings.
  • Metrics — three cards that summarize the entries on screen.
  • Search and filters — a search box, a Filters panel, category tabs, and Reset.
  • Table — one row per entry, with Time, Level, Source, Function, and Message columns.
Each row’s Time shows the date and how long ago the event happened. The Message for a GraphQL request shows the status code, the operation type (query or mutation), the operation name, the latency, and a short text such as gateway ingress. At the bottom of the table, Rows per page sets how many entries you see at once (10, 25, 50, or 100). A counter such as “Showing 1 to 25 of 69 entries” shows where you are in the results.

​
Metrics

Three cards sit above the table:
The metrics use only the entries loaded for the selected range. When you change the time range or apply a filter, the numbers change with it.

​
Search and filter

Select the magnifying glass to open the search bar. Pick what to search with the selector on the left:
  • Message searches the message text.
  • GraphQL searches GraphQL requests, for example by operation name.
Type your term, or pick one of the suggestions Archie offers from your own logs. Suggestions include quick filters such as Failed operations, Mutations, Queries, Server errors (5xx), and Client errors (4xx), followed by operation names found in your logs. Select Apply to run the search. Select Reset to clear the search and filters.

​
Category tabs

The tabs above the table narrow the list to one category of entry: All, Request, Logic, Integrations, Files, and Errors. A tab with no matching entries shows No logs found.

​
Filter by level, source, and time

Select Filters to open the filter panel. The Filters panel with Level, Source, and Time selectors and the System operations toggle Turn on System operations to include system-generated operations, such as GetDatabaseTables and QueryTable. These entries are hidden until you turn the toggle on, so the entry count goes up when you enable it.

​
Read an entry

Select a row to expand it. The detail shows:
  • Status — the HTTP status code.
  • Operation — the operation type and name.
  • Fields accessed — the top-level GraphQL fields the request touched.
  • Method — the HTTP method.
  • Latency — how long the request took.
  • Path — the request path, for example /graphql.
  • User — the user the request ran as.
  • Raw event — the full entry as JSON.
Select Copy next to Raw event to copy the JSON, for example to paste it into a bug report.
Raw events and the User field can contain user identifiers. Remove them before you share a log entry outside your team.

​
Live tail

Select Live tail to watch new entries arrive without refreshing. A LIVE badge appears next to the page title and the button changes to Live. Select Live again to stop. Select Refresh to load the latest entries on demand.

​
Change the row density

Use the density toggle to switch between Comfortable and Compact. Compact fits more rows on screen by shortening each row. The Logs page in Compact density with Live tail turned on

​
Export

Select Export to download the entries in the current view. The menu offers Download JSON and Download CSV, and each option shows how many rows it will include.

​
Log settings

Select Log settings to open the settings drawer. The Log settings drawer showing Capture level, Retention options, and Alerts

​
Capture level

Capture level sets the lowest level Archie stores: Debug, Info, Warn, or Error. Entries below the level are not stored. You set it per environment.
Capture level is marked Coming soon. You can see the control, but you can’t change it yet.

​
Retention

Retention sets how long logs are kept before they age out. The option you can use depends on your plan: Your current retention is selected. Options your plan doesn’t include show an Upgrade link.

​
Alerts

Alerts will notify you when the error rate or latency crosses a threshold. It’s marked Coming later.

​
FAQ and troubleshooting

Check these in order:
  1. Confirm you’re in the right project and environment. Logs are scoped to both.
  2. Widen Time. The default is Last hour, so older entries stay hidden until you choose a longer range.
  3. Select Reset to clear any search, category tab, or filter.
  4. Check Source and Level. A narrow selection can hide the entries you want.
  5. Turn on System operations if you expect entries from system-generated requests.
  6. Select Refresh to load the latest entries.
Logs older than your plan’s retention period are no longer available. See Retention.
The metrics describe the entries loaded for the selected range. A different time range, search, or filter changes which entries are loaded, so the numbers change too.
No. Logs shows only the current project, and the environment selected in the Backend Console.
Start with the task’s run history. It links to the full request and response in Logs.