About the Logs menu

The Logs menu contains links to two pages that provide access to log data for your services:

• Tailing: 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: allows you to view, filter, and analyze 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 guide.

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 web interface.
2. Go to Observability > Logs > Tailing.

About the Explorer page

The Explorer page allows you to view, filter, and analyze log entries for a service.

For each 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.
• URL: the URL of the requested asset.

You can click any log entry to reveal more data about the request. When available, the following data is provided.

You can filter the 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.

Accessing the Explorer page

To access the Explorer page:

1. Log in to the Fastly web interface.
2. Go to Observability > Logs > Explorer.

What's next