--- title: "[Contentstack Launch] - Live Logs and Server Logs" description: Live Logs and Server Logs in Contentstack Launch url: https://www.contentstack.com/docs/launch/live-logs-and-server-logs product: Contentstack Launch doc_type: guide audience: - developers version: unknown last_updated: unknown --- # [Contentstack Launch] - Live Logs and Server Logs This page explains how to use Live Logs and Server Logs in Contentstack Launch to inspect runtime server logs for a deployment. It is intended for developers and operators who need to monitor applications in real time or investigate issues after they occur, and should be used when troubleshooting runtime behavior in Launch deployments. ## Live Logs and Server Logs Contentstack Launch provides two views for inspecting the runtime server logs generated by your deployment: - **Live Logs:** A real-time streaming view - **Server Logs:** A historical on-demand view Both are available under the Logs section on the deployment detail page and share the same Search and Source filters. **Note:** This document does not cover Deployment Logs, which show output from the build and deploy pipeline. Refer to the [Deployments](/docs/developers/launch/deployments) documentation for details on Deployment Logs. ## Prerequisites - [Contentstack account](https://www.contentstack.com/login/) - Access to Launch for your organization - A project already deployed in Launch that you have access to. ## Live Logs The Live Logs feature in Contentstack Launch streams runtime server logs from your deployed application in real time. These are the logs your application emits as it handles requests, distinct from the Deployment Logs generated by the build and deploy pipeline. Use Live Logs to watch output as it is generated, for example, when reproducing a runtime issue. Each session runs for a maximum of **5 minutes** and ends automatically, after which the captured entries remain available in Server Logs. ### Start a Live Logs Session To start a Live Logs session, follow the steps below: - Open the deployment you want to monitor. - Under **Logs**, select the **Server Logs** view. - Click the **Live Log Capture** button at the top right of the toolbar. Before any entries arrive, the log panel displays `Waiting for logs…`. Entries begin streaming into the panel as soon as your application produces log output. ### View Streaming Logs Log entries appear in the panel as they are generated. Each entry shows its source (**Origin **or **Edge**) and includes a timestamp accurate to the millisecond (`HH:mm:ss.SSS`). A countdown badge in the toolbar (for example, `Live · 0:46`) shows how much time remains in the current session. **Note:** Only the most recent **1,000 log lines** are visible at a time; earlier lines are no longer displayed. ### Pause, Resume, or End a Session The toolbar provides three controls while a session is active: - **Clear logs:** Clears the entries currently displayed. New entries continue to stream in. - **Pause logs:** Freezes the display. The session continues to capture entries in the background. The badge switches to `**Paused · [time remaining]**`, and a message above the panel shows how many entries have arrived. For example: `Paused: 103 new logs received. Resume to view`. Click **Resume** to reveal them and continue streaming. - **End Session:** Ends the session immediately after a confirmation. ### Filter Live Logs Live Logs supports two filters: - **Search:** Filters entries by log message text. - **Source:** Origin, Edge, or both. At least one source must remain selected. ### Session Duration and Auto-End A Live Logs session ends automatically after **5 minutes**. The panel then freezes as a snapshot, and a banner appears with two options: - **View server logs:** Switches to Server Logs, where the captured entries remain visible alongside the historical logs. - **Keep viewing snapshot:** Keeps the frozen snapshot in the panel for review. **Note:** To keep monitoring beyond **5 minutes**, start a new session by clicking **Live Log Capture** again, or switch to **Server Logs** and refresh manually. ### Leaving the Page During a Live Logs Session If you try to navigate away while a Live Logs session is active, an **End Live Session?** dialog appears, showing how much time is left in the session (for example, `3:37 still remaining`). - **Continue Live:** Cancels the navigation and keeps you in the session. - **End Session:** Confirms the navigation and ends the session. ### Refreshing the Page During a Live Logs Session Refreshing your browser while a Live Logs session is ongoing ends the session automatically. The entries generated during that period are preserved and remain accessible for review within the **Server Logs** section. ## Server Logs The Server Logs feature in Contentstack Launch lets you review runtime server logs generated by your deployment on demand. Use it to investigate an issue after it has occurred, or to look back over recent activity. Server Logs is the default view under Logs and does not auto-refresh. To see new entries, refresh manually or use Live Log Capture for real-time streaming. ### View Server Logs To view Server Logs for a deployment, follow the steps below: - Open the deployment you want to inspect. - Under Logs, select the **Server Logs** view (the default). A banner at the top reminds you that Server Logs does not auto-refresh: `Server logs no longer auto-refresh. Refresh manually to load new entries, or use Live Log Capture for real-time streaming.` ### Load Older and Newer Logs Server Logs loads entries in batches of 200. Each load adds **200 entries** at one end of the list and removes **200 entries** from the opposite end, so the visible list stays a manageable size. - **Load previous logs:** Located above the log list. Adds the **200 older entries** immediately preceding the currently displayed range, and removes **200 entries** from the bottom. - **Load new logs:** Located below the log list. Adds the **200 newer entries** generated since the last load and removes **200 entries** from the top. - **Refresh:** A toolbar control that reloads the current view. ### Filter Server Logs Server Logs supports three filters: - **Search:** Filters entries by log message text. - **Source:** **Origin**, **Edge**, or both. At least one source must remain selected. - **Limit:** Maximum rows displayed: **500 (default)**, **1,000**, **3,000**, or **5,000**. **Note:** Additional icons above the log list let you jump to the top or bottom of loaded entries and copy the visible logs. ### Loading, Empty, and Error States Server Logs display a distinct state for each outcome: - **Loading:** A loading indicator appears while the panel fetches entries. - **Empty:** When no entries match the current filters, the panel shows `No server logs to show at the moment.` - **Error:** When a fetch fails, a distinct error message appears. So a failed refresh is never confused with a genuinely empty log list. ### Switch to Live Logs from Server Logs To start monitoring in real time, click **Live Log Capture** in the toolbar. This starts a new Live Logs session for the same deployment. Entries captured during the session remain visible in Server Logs after the session ends. ## Limits ### Live Logs - A session runs for a maximum of **5 minutes**. ### Server Logs - Maximum lookback of **24 hours**. To retain logs beyond this window, configure a [Log Target](/docs/launch/log-targets). - Maximum of **5,000 rows** per view. - Does not auto-refresh. ## Common questions ### What is the difference between Live Logs and Server Logs? Live Logs is a real-time streaming view, while Server Logs is a historical on-demand view. ### How long does a Live Logs session run? A session runs for a maximum of **5 minutes** and ends automatically. ### Do Server Logs refresh automatically? No. Server Logs does not auto-refresh; refresh manually to load new entries, or use Live Log Capture for real-time streaming. ### How far back can Server Logs look? Server Logs has a maximum lookback of **24 hours**.