1. Home
2. Guides
3. Observability
4. Observability Dashboards

The Services menu contains links to two pages that display high-level metrics for your services:

• Service Overview: page that contains the Service Overview dashboard, which displays different information depending on if you are viewing a Deliver or Compute service.
• All Services: page that contains the All Services dashboard, which displays aggregated metrics from all of your services.

To access the Services menu, go to Observability > Services.

Before you begin

Be sure you know how to access the web interface controls before learning about the details you'll encounter here.

About the Service Overview page

The Service Overview page gives you access to the Service Overview dashboard, which displays different information depending on if you are viewing a Deliver or Compute service.

Service Overview dashboard for a Deliver service

When a Deliver service is selected from the Service menu, the Service Overview dashboard displays metrics that help you understand your service's cache performance, traffic, and errors.

How is my cache performing?

These metrics help you understand how effectively your Fastly service is caching content and how that affects response times.

• Hit Ratio: the percentage of cache hits to all cacheable content over time.
• Cache Coverage: the percentage of your site that you are caching with Fastly.
• Misses: the number of cache misses.
• Hit Time: the average amount of time spent processing cache hits.
• Miss Time: the average amount of time spent processing cache misses.
• Object Sizes: the number of objects served by payload size.

How much work is hitting my origin?

These metrics show how much traffic is reaching your origin and how quickly your origin is responding.

• Origin Offload: the percentage of bytes served to end users that were cached by Fastly.
• Origin Latency: the distribution of origin latency times that approximate how quickly your origin is responding to Fastly. This histogram only appears when you are viewing live traffic.
• Origin Latency Percentiles: the origin latency percentiles that approximate how quickly your origin is responding to Fastly. Each percentile is indicated by pn, where n is the percentile number. pn means n% of all requests had an origin latency value that is less than or equal to the value on the y-axis. For example, if the value of p95 is 8s, 95% of all requests had an origin latency that was less than or equal to 8 seconds. This graph only appears when you are viewing live traffic.

What does my traffic look like?

These metrics show the volume, shape, and protocol characteristics of requests reaching your service.

• Global POP Traffic: the map of Fastly's points of presence (POPs) that receive requests for your service. The map only appears when you are viewing live traffic.
• Requests: the number of requests by cache response type.
• Requests Per Second: the average number of requests per second. This metric does not appear when you are viewing live traffic.
• HTTP Versions: the number of requests using HTTP/1.1, HTTP/2, and HTTP/3(QUIC).
• TLS Versions: the number of requests using TLS 1.0, TLS 1.1, TLS 1.2, and TLS 1.3 protocols.

How is bandwidth being used?

These metrics track how much data Fastly is transferring on behalf of your service.

• Bandwidth: the average bandwidth served per second by Fastly.
• Total Bandwidth: the total bytes served by Fastly. This metric does not appear when you are viewing live traffic.
• Header & Body Bytes Transferred: the relative values of bytes transferred when serving the body and header portions of HTTP requests.

Are errors affecting my users?

These metrics help you identify error rates across your service, broken down by status code category and region.

• All Status Codes: the number of responses sent by status group.
• Error Ratio: the number of cache errors.
• Error Ratio by Region: the percentage of cache errors per region.
• Status 3XX Details: the number of HTTP status 301s, 302s, 304s, and other 3XX requests.
• Status 4XX Details: the number of HTTP status 400s, 401s, 403s, 404s, 416s, 427s, and other 4XX requests.
• Status 5XX Details: the number of HTTP status 500s, 501s, 502s, 503s, 504s, 505s, and other 5XX requests.

What's happening with my logging pipeline?

These metrics track the volume of log data flowing from Fastly to your configured endpoints.

• Log Lines: the number of log lines sent.
• Total Log Bandwidth: the total log bytes sent to your endpoints from Fastly.

The dashboard also displays collections of metrics that you can expand and collapse by clicking the collection name. The collections include:

• Image Optimizer: metrics for your services that relate to image optimization.
• WebSockets: metrics for your service that relate to WebSockets.
• Fanout: metrics for your service that relate to Fanout.

Service Overview dashboard for a Compute service

When a Compute service is selected from the Service menu, the Service Overview dashboard displays metrics that help you understand your service's traffic, resource consumption, and errors.

What does my traffic look like?

These metrics show the volume of requests reaching your service and how they're being categorized.

• Global POP Traffic: a map of Fastly's points of presence (POPs) that receive requests for your service.
• Requests: the total number of requests received for your service by Fastly.
• Requests Per Second: the average number of requests per second. This metric does not appear when you are viewing live traffic.
• Response Status Codes: the total number of response status codes by category delivered by Compute.

How is bandwidth being used?

These metrics track how much data is flowing between clients, Fastly, and your origins.

• Bandwidth: the average bandwidth served per second by Fastly.
• Total Bandwidth Received from Client: the total bytes received from the client.
• Total Bandwidth Transferred to Client: the total bytes served by Fastly.
• Total Bandwidth Sent to Backend: the total bytes sent to backends (origins) by Compute.
• Total Bandwidth Received from Backend: the total bytes received from backends (origins) by Compute.

How are my service's resources being consumed?

These metrics show how much compute capacity your service is using to process requests.

• Total Wall Clock Time: the total, actual amount of time used to process your requests, including active CPU time.
• CPU Time: the amount of active CPU time used to process your requests.
• RAM Usage: the amount of RAM used for your service by Fastly (in bytes).
• Cache Operations per Request: the average number of cache operations per request.

Are errors affecting my service?

Compute error metrics fall into three categories based on where in the request lifecycle the error occurs.

Resource limits errors indicate that your service reached a platform-enforced maximum.

• Sandbox Timeout: the number of times the sandbox reached the maximum wall-clock runtime limit.
• Memory Exceeded: the number of times the sandbox consumed the maximum memory (heap) allocated by the platform.
• vCPU Exceeded: the number of times the sandbox exceeded the maximum active processing (vCPU) time.

Runtime and logic errors are triggered during service execution and request routing.

• Runtime Errors: the number of fatal errors during service code execution due to WebAssembly (Wasm) traps, invalid service logic, or prohibited actions.
• Service Chain Errors: the number of errors when a request exceeded limits related to service chaining or circular dependencies.
• Service Limits: the number of non-fatal errors when service code attempts an operation that exceeds a specific functional threshold.
• Backend Request Errors: the number of failed attempts to communicate with a backend (origin).

Platform errors are internal failures and malformed external requests that prevent service code from executing.

• Internal Platform Errors: the number of internal system events indicating that the platform was unable to initialize or maintain the execution environment for your service.
• Invalid Request Errors: the number of malformed external requests rejected by the Compute platform before they can be processed by your service code.

What's happening with my logging pipeline?

These metrics track the volume of log data flowing from Fastly to your configured endpoints.

• Logs: the number of logs sent to your endpoints from Fastly.
• Total Log Bandwidth: the total log bytes sent to your endpoints from Fastly.

About the All Services page

The All Services page gives you access to the All Services dashboard, which displays aggregated metrics from all of your services. Specifically, it displays the following overview metrics:

• Requests: a graph displaying the number of requests served across your account.
• Bandwidth: a graph displaying the number of bytes served from Fastly's servers to your website's visitors.
• Error Ratio: a graph displaying the number of cache errors across your account.

The dashboard also displays collections of metrics that you can expand and collapse by clicking the collection name. The collections include:

• Deliver: aggregated metrics from all of your Deliver services. The metrics in this collection mirror the metrics on the Service Overview dashboard for a Deliver service.
• Compute: aggregated metrics from all of your Compute services. The metrics in this collection mirror the metrics on the Service Overview dashboard for a Compute service.
• Image Optimizer: aggregated metrics from all of your services that relate to Image Optimizer.
• WebSockets: aggregated metrics from all of your services that relate to WebSockets.
• Fanout: aggregated metrics from all of your services that relate to Fanout.
• Media Shield: aggregated metrics for your service that relate to Media Shield.

About the Image Optimizer metrics collection

The Image Optimizer metrics collection appears on the Service Overview dashboard for a Deliver service and on the All Services dashboard. These metrics help you understand how much image optimization traffic Fastly is handling for your service, including the split between direct and shield-routed delivery.

• Image Optimizer total responses: the total number of responses that came from the Fastly Image Optimizer service.
• Image Optimizer shield responses: the number of responses that came from the Fastly Image Optimizer service via a shield.
• Image Optimizer total bytes delivered: the total bytes delivered from the Fastly Image Optimizer service, including shield traffic.
• Image Optimizer shield bytes delivered: the total bytes delivered via a shield from the Fastly Image Optimizer service.
• Image Optimizer video responses: the number of video responses that came from the Fastly Image Optimizer service.
• Image Optimizer video frames: the number of video frames that came from the Fastly Image Optimizer service. A video frame is an individual image within a sequence of video.
• Image Optimizer video bytes delivered: the total bytes of video delivered from the Fastly Image Optimizer service.
• Image Optimizer video shield responses: the number of video responses delivered via a shield that came from the Fastly Image Optimizer service.
• Image Optimizer video shield bytes delivered: the total bytes of video delivered via a shield from the Fastly Image Optimizer service.
• Image Optimizer video shield frames: the number of video frames delivered via a shield that came from the Fastly Image Optimizer service. A video frame is an individual image within a sequence of video.

About the WebSockets metrics collection

The WebSockets metrics collection appears on the Service Overview dashboard for a Deliver service and on the All Services dashboard. These metrics help you understand how much bandwidth and connection time your WebSocket traffic is consuming across clients, Fastly, and your origin.

• WebSockets connection time: the total duration of passthrough WebSocket connections with end users.
• WebSockets bytes transferred to client: the total bandwidth transferred by Fastly for your service when using requests.
• WebSockets bytes transferred from client: the total bandwidth transferred by Fastly for your service when receiving requests.
• WebSockets bytes transferred to origin: the total bandwidth transferred by Fastly to your backend when receiving requests.
• WebSockets bytes transferred from origin: the total bandwidth transferred to Fastly from your backend when serving requests.

About the Fanout metrics collection

The Fanout metrics collection appears on the Service Overview dashboard for a Deliver service and on the All Services dashboard. These metrics help you understand how much bandwidth, connection time, and message volume your Fanout traffic is generating across clients, Fastly, and your backend.

• Fanout connection time: the total duration of Fanout connections with end users.
• Fanout published messages: the total number of messages received from the publish API and sent to end users.
• Fanout bytes transferred to client: the total bandwidth transferred by Fastly for your service when serving requests.
• Fanout bytes transferred from client: the total bandwidth transferred by Fastly for your service when receiving requests.
• Fanout bytes transferred to backend: the total bandwidth transferred by Fastly to your backend when receiving requests.
• Fanout bytes transferred from backend: the total bandwidth transferred to Fastly from your backend when serving requests.

About the Media Shield metrics collection

The Media Shield metrics collection appears on the Service Overview dashboard for a Deliver service. These metrics help you understand how Media Shield is handling requests across edge and shield layers.

How is Media Shield caching content?

These metrics show cache performance at both the edge and the Media Shield layer.

• Media Shield Hit Ratio: the percentage of cache hits to all cacheable content at the Media Shield over time.
• Edge Hit Ratio: the percentage of cache hits to all cacheable content at the edge over time.
• Origin Offload: the ratio of bytes served to end users that were cached.
• Request Collapsing: the number of requests that were collapsed and either satisfied by a usable cache object or unable to be satisfied by the resulting cache object.

What does Media Shield traffic look like?

These metrics track the volume of requests and data flowing through Media Shield.

• Media Shield Requests: the number of requests sent to Media Shield.
• Media Shield Bytes: the number of bytes sent to Media Shield.
• Media Shield Fetches: the number of requests from one Fastly POP to another as part of Media Shield.
• Requests by Domain Name: the number of requests broken out by domain name.

How are requests distributed across layers?

These metrics show where requests are being served from and where they're resulting in misses.

• Media Shield Hit Requests: the average number of requests that hit the Media Shield.
• Media Shield Miss Requests: the average number of requests that missed at the Media Shield.
• Edge Miss Requests: the average number of requests that resulted in a miss at the edge.

What's next

Dig deeper into details about all areas of the web interface before you move on to working with services.