--- title: About the Logs menu summary: null url: >- https://www.fastly.com/documentation/guides/observability/observability-dashboards/about-the-logs-menu --- The Logs menu contains links to two pages that provide access to log data for your services: - **[Tailing](https://www.fastly.com/documentation/guides/observability/observability-dashboards/about-the-logs-menu#about-the-tailing-page):** provides access to Compute log tailing, allowing you to view custom log messages from your Compute application. Specifically, the Tailing feature streams your Compute application's logs to the Fastly control panel so you can debug your application without setting up a third-party logging tool. - **[Explorer](https://www.fastly.com/documentation/guides/observability/observability-dashboards/about-the-logs-menu#about-the-explorer-page):** allows you to view, filter, and analyze request log entries for a service. All data is sampled. ## Before you begin The Explorer page is part of the Log Explorer & Insights feature, which is disabled by default. To enable this feature, refer to the [About the Insights page](https://www.fastly.com/documentation/guides/observability/observability-dashboards/about-the-insights-page) guide. Be sure you know how to [access the web interface controls](/guides/getting-started/navigating-fastly/about-the-web-interface-controls) before learning about the details you'll encounter here. ## About the Tailing page The Tailing page provides a real-time live stream of the log outputs for a Compute service. Streamed outputs can include any output sent to the standard output stream (`stdout`) and the standard error stream (`stderr`), as well as any runtime errors encountered by the application. For each log, the Tailing page displays the following information: - **Date (UTC):** a UTC timestamp of when the request occurred. - **Request ID:** a unique identifier applied to the request. - **Event:** the event type, either `stdout` or `stderr`. - **Message:** the message included in the request. A series of controls on the Tailing page allow you to interact with and refine the logs. Specifically: - the **Service** menu allows you to specify the Compute service that the logs are from. From the menu, you can search for a service by ID or name. - the **Events** menu allows you to limit the displayed logs to a specific stream (e.g., `stdout` and `stderr`). - the **Pause** button allows you to pause the live stream of Compute logs. Once paused, you can resume live stream by clicking **Live**. ### Accessing the Tailing page To access the Tailing page: 1. Log in to the [Fastly control panel](https://manage.fastly.com). 2. Go to **Observability** > **Logs** > [**Tailing**](https://manage.fastly.com/observability/logs/tail). ## About the Explorer page The **Explorer** page allows you to view, filter, and analyze request log entries for a service. > **HINT:** To support performance at scale, we sample data at a set rate determined by the requests per second (RPS) of your service. The sample is large enough to provide statistically significant insights, but it doesn't contain all of the request log entries for your service. ### Accessing the Explorer page To access the Explorer page: 1. Log in to the [Fastly control panel](https://manage.fastly.com). 2. Go to **Observability** > **Logs** > [**Explorer**](https://manage.fastly.com/observability/logs/explorer). ### Available data For each request log entry, the Explorer page displays the following information: - **Date (UTC):** a UTC timestamp of when the request occurred. - **Status Code:** the HTTP status code of the response. - **Region:** the region from which the request originated. - **POP:** the POP that received the request. - **Cache Status:** the status indicating whether the request was a HIT or a MISS. A request can have multiple statuses based on clustering and shielding configurations. The last status in the list indicates the ultimate status of a request. This information is not available for Compute services. - **URL:** the URL of the requested asset. You can click any request log entry to reveal more data about the request. To expand all request log entries on the page, click the expand all icon Expand all icon. When available, the following data is provided. | Field | Service Type Availability | Description | | ------------------------- | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `customer_id` | CDN and Compute | Your Fastly customer ID. | | `service_id` | CDN and Compute | The Fastly service ID. | | `timestamp` | CDN and Compute | The timestamp of when the request occurred. | | `client_as_name` | CDN and Compute | The name of the organization associate with `client.as.number`. | | `client_as_number` | CDN | The autonomous system (AS) number. | | `client_browser_name` | CDN | The name of the web browser the client was using. | | `client_browser_version` | CDN | The version of the web browser the client was using. | | `client_country_code` | CDN | The country from which the request originated. | | `client_device_type` | CDN | The type of device the client was using. | | `client_ip_prefix` | CDN and Compute | The truncated IP address of the client making the HTTP request. We discard the parts of the IP address that could be considered personally identifiable information (PII). | | `client_os_name` | CDN | The name of the operating system installed on the client device. | | `client_os_version` | CDN | The version of the operating system installed on the client device. | | `client_ploss` | CDN | The estimate of packet loss associated with the client-side connection. | | `client_region` | CDN | The region from which the request originated. | | `client_rtt` | CDN | The TCP stack's smoothed round trip time (RTT) estimate, in microseconds, for the current connection to the client. | | `fastly_pop` | CDN and Compute | The name of the Fastly POP that served the request. | | `fastly_server` | CDN and Compute | The hostname of the cache server. | | `origin_host` | CDN and Compute | The name of the origin host that served the request. | | `origin_ip` | CDN and Compute | The IP address of the origin host that was used for the request. | | `origin_reason` | CDN and Compute | The HTTP response phrase received from the backend. | | `origin_status` | CDN | The HTTP status code of the response received from the backend. | | `origin_ttfb` | CDN and Compute | The time to first byte for responses received from the backend. | | `origin_ttlb` | CDN and Compute | The time to last byte for responses received from the backend. | | `request_protocol` | CDN and Compute | The HTTP protocol version in use for the request. | | `request_host` | CDN and Compute | The host the request was made to. | | `request_path` | CDN and Compute | The path of the requested asset. | | `request_method` | CDN and Compute | The HTTP method sent by the client, such as `GET` or `POST`. | | `request_restarts` | CDN | The number of times the VCL has been restarted. | | `request_tls_ja3_md5` | CDN and Compute | The JA3 fingerprint computed from the TLS Client Hello packet. | | `request_tls_version` | CDN and Compute | The TLS protocol version the connection is speaking over. | | `requested_range` | CDN and Compute | Part of the range header from the origin that's logged as `req.http.range`. | | `response_age` | CDN | Total age of the object. | | `response_bytes_body` | CDN and Compute | The size of the response body in bytes. | | `response_bytes_header` | CDN and Compute | The size of the response header in bytes. | | `response_cache_control` | CDN and Compute | The `Cache-Control` header from the origin. | | `response_completed` | CDN | Indicates if the edge Varnish has transmitted the entire response header and body. | | `response_content_length` | CDN and Compute | The size of the response content in bytes. | | `response_content_type` | CDN and Compute | The type of content in the response. | | `response_reason` | CDN and Compute | The response phrase included with the HTTP status code. | | `response_state` | CDN | State of the request. | | `response_status` | CDN and Compute | The HTTP response code returned for the request. | | `response_time` | CDN and Compute | The amount of time it took to respond to the request. | | `response_ttfb` | CDN and Compute | The time interval since the request started up to the before the `vcl_deliver` subroutine ran. | | `response_ttl` | CDN and Compute | The maximum amount of time for which the object will be considered fresh in the cache. | | `response_x_cache` | CDN and Compute | Indicates whether the request was a HIT or a MISS. | | `is_cache_hit` | CDN | Indicates whether this request was fulfilled from cache. | | `is_edge` | CDN and Compute | Indicates whether the request was handled by a Fastly edge POP. | | `is_shield` | CDN | Indicates whether the request was handled by a Fastly shield POP. | ### Filtering log entries You can filter the request log entries displayed on this page by: - selecting the **Service** the request was made to. - entering the **Domain** the request was made to. - entering the **URL path** the request was made to. - selecting the **Response Status** to filter by the HTTP status code of the response. - selecting the **Point of Presence** that received the request. - selecting the **Browser** the client was using. - selecting the **Operating system** installed on the client device. - selecting the **Device type** that the client was using. - selecting the **Cache status** of the response. - selecting the **Fastly Edge** status of the response. - selecting the **Fastly Shield** status of the response. - specifying the range of **Response Time** of the response. - specifying a **Time Range** for log entries. #### Using custom filters You can use custom filters in addition to the standard filters. To add a custom filter: 1. In the **Custom filters** section of the filter controls, click **Add custom filter**. 2. From the field menu, select the field to filter by. Fields are grouped by category (e.g., Client, Origin, Request, and Response). 3. From the operator menu, select an operator (e.g., **is** or **contains**). The menu only displays the operators supported by the selected field. 4. Enter or select a value for the filter. The **is one of** and **is not one of** operators accept multiple values. 5. Click **Apply**. You can create multiple custom filters. Custom filters are combined with each other and with the standard filters using AND logic, so only the request log entries that match every filter are displayed. To remove a custom filter, click the remove button next to the filter. ### Exporting log data You can export the request log entries displayed on the page by clicking **Export to CSV**. This automatically downloads a CSV-formatted text file to a local directory. ## What's next Dig deeper into details about all areas of the [web interface](/guides/getting-started/navigating-fastly) before you move on to [working with services](/guides/getting-started/services/about-services). ## Related content - [Log Explorer API documentation](https://www.fastly.com/documentation/reference/api/observability/log-explorer/)