---
title: "Academy Article"
canonical_url: "https://academy.laioutr.com/en/artikel/read-storefront-logs"
locale: en
meta:
"og:title": "Academy Article"
---
[Go to home](https://academy.laioutr.com/en)
- [Hosting and operations](https://academy.laioutr.com/en/bereiche/hosting-and-operations)
- [Deployment](https://academy.laioutr.com/en/leitfaeden/deployment)
- [Read storefront logs](https://academy.laioutr.com/en/artikel/read-storefront-logs)
# Read storefront logs
Under Logs, Cockpit shows what the storefront of each environment on Laioutr Cloud writes, plus an access log. Each line's level comes from the console method that was called, and a trace finds all lines of one request.
## Before you start
- Plan
- Laioutr Cloud
- Role
- Access to the project in Cockpit
- Duration
- 6 min
### Prerequisites
- A deployed environment on Laioutr Cloud
Last reviewed on October 15, 2026
**Logs** in Cockpit shows the output of the storefront for every environment on Laioutr Cloud and a copy of the access log with one line per served request. It helps narrow down errors after a deployment or on individual pages.
### Where a level comes from
Laioutr Cloud does not guess the level from the text but takes it from the method that was called: `console.log` and `console.info` give Info, `console.debug` Debug, `console.warn` Warning, and `console.error` plus errors that Nuxt and Nitro log for a request give Error. Libraries that write to stdout themselves show as Info, to stderr as Error.
### Access log
Responses with status 5xx show as Error, 4xx and requests without a response as Warning, everything else as Info. The visitor's IP address is not included.
One call is one entry; the stack trace and passed objects stay together. An entry keeps 16 KiB of its message, the rest is cut and marked.
## Step by step
1. 1 ### Step 1: Open Logs Open **Logs** in the project in Cockpit.
2. 2 ### Step 2: Choose the environment Choose the environment whose logs should be shown, for example main or stage.
3. 3 ### Step 3: Filter by level Narrow down to Error or Warning with the level filter to find errors quickly.
4. 4 ### Step 4: Follow one request Open a trace and select **Logs of this request**. Cockpit then shows every line that request wrote.
5. 5 ### Step 5: Check the access log Look for lines with level Error in the access log; they stand for responses with status 5xx.
## Check the result
The Error filter shows the expected error lines for the selected environment, and a test request to a page appears as a line in the access log.
## Frequently asked questions
Why does a warning show as Error?
consola writes warn and error to the same stream, so both show as Error. pino writes every level to stdout, so its errors show as Info. To log a warning with level Warning, use `console.warn`.
Why does a line have no trace?
Not every request is traced. Lines from a request without a trace carry no reference.
How long are logs kept?
Five days by default. For 30 days, Laioutr support moves the environment to extended observability.
Where are the logs of a build?
Build logs belong to their deployment and are shown in its detail view under **Deployments**.
## Related
- [Start and check a deployment](https://academy.laioutr.com/en/artikel/start-and-check-a-deployment)5 min
A deployment rebuilds the storefront of an environment and puts changes to apps, versions and configuration live. It is started in Cockpit under Deployments with Deploy; the status and build log show whether it worked.
- [Compare and roll back deployments](https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments)5 min
Every deployment has its own address, so two versions can be compared side by side. A rollback puts an already built earlier production deployment live again within seconds, without a new build.
- [Set up a local development environment](https://academy.laioutr.com/en/artikel/set-up-a-local-development-environment)15 min
With the App Starter, a login to the Laioutr npm registry and the project configuration from Cockpit, a custom Laioutr app runs locally within minutes. The Studio command Developer: Use Localhost then shows the local version directly in Studio.
## Learn it in a lesson
- [Check the deployment status](https://academy.laioutr.com/en/lektionen/foundations-deployment-status)7 min
- [Domains, CDN and logs](https://academy.laioutr.com/en/lektionen/developer-domains-cdn-and-logs)10 min
- [Start and check a deployment](https://academy.laioutr.com/en/lektionen/go-live-start-and-check-a-deployment)7 min
## [Deployment](https://academy.laioutr.com/en/leitfaeden/deployment)
Search this guide
1. [Understanding the main, dev and stage environments](https://academy.laioutr.com/en/artikel/understanding-main-dev-and-stage-environments)5 min
2. [Start and check a deployment](https://academy.laioutr.com/en/artikel/start-and-check-a-deployment)5 min
3. [Compare and roll back deployments](https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments)5 min
4. [Read storefront logs](https://academy.laioutr.com/en/artikel/read-storefront-logs)6 min
5. [Bring Your Own Server: host the storefront in-house](https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house)7 min In preparation
## Structured Data
```json
{
"@context": "https://schema.org",
"@graph": [
{
"@id": "https://academy.laioutr.com/#website",
"@type": "WebSite",
"inLanguage": "en",
"name": "Default",
"url": "https://academy.laioutr.com/",
"translationOfWork": {
"@id": "https://academy.laioutr.com/#website"
}
},
{
"@id": "https://academy.laioutr.com/en/artikel/read-storefront-logs#webpage",
"name": "Academy Article",
"url": "https://academy.laioutr.com/en/artikel/read-storefront-logs",
"@type": [
"WebPage",
"FAQPage"
],
"breadcrumb": {
"@id": "https://academy.laioutr.com/en/artikel/read-storefront-logs#breadcrumb"
},
"isPartOf": {
"@id": "https://academy.laioutr.com/#website"
},
"mainEntity": [
{
"@id": "https://academy.laioutr.com/en/artikel/read-storefront-logs#/schema/question/1"
},
{
"@id": "https://academy.laioutr.com/en/artikel/read-storefront-logs#/schema/question/2"
},
{
"@id": "https://academy.laioutr.com/en/artikel/read-storefront-logs#/schema/question/3"
},
{
"@id": "https://academy.laioutr.com/en/artikel/read-storefront-logs#/schema/question/4"
}
],
"potentialAction": [
{
"@type": "ReadAction",
"target": [
"https://academy.laioutr.com/en/artikel/read-storefront-logs"
]
}
]
},
{
"@id": "https://academy.laioutr.com/en/artikel/read-storefront-logs#breadcrumb",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"name": "Home",
"item": "https://academy.laioutr.com/en",
"position": 1
},
{
"@type": "ListItem",
"name": "Hosting and operations",
"item": "https://academy.laioutr.com/en/bereiche/hosting-and-operations",
"position": 2
},
{
"@type": "ListItem",
"name": "Deployment",
"item": "https://academy.laioutr.com/en/leitfaeden/deployment",
"position": 3
},
{
"@type": "ListItem",
"name": "Read storefront logs",
"item": "https://academy.laioutr.com/en/artikel/read-storefront-logs",
"position": 4
}
]
},
{
"@id": "https://academy.laioutr.com/en/artikel/read-storefront-logs#/schema/question/1",
"@type": "Question",
"inLanguage": "en",
"name": "Why does a warning show as Error?",
"acceptedAnswer": {
"@type": "Answer",
"text": "consola writes warn and error to the same stream, so both show as Error. pino writes every level to stdout, so its errors show as Info. To log a warning with level Warning, use console.warn.
"
}
},
{
"@id": "https://academy.laioutr.com/en/artikel/read-storefront-logs#/schema/question/2",
"@type": "Question",
"inLanguage": "en",
"name": "Why does a line have no trace?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Not every request is traced. Lines from a request without a trace carry no reference.
"
}
},
{
"@id": "https://academy.laioutr.com/en/artikel/read-storefront-logs#/schema/question/3",
"@type": "Question",
"inLanguage": "en",
"name": "How long are logs kept?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Five days by default. For 30 days, Laioutr support moves the environment to extended observability.
"
}
},
{
"@id": "https://academy.laioutr.com/en/artikel/read-storefront-logs#/schema/question/4",
"@type": "Question",
"inLanguage": "en",
"name": "Where are the logs of a build?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Build logs belong to their deployment and are shown in its detail view under Deployments.
"
}
}
]
}
```