About the stats for Compute services

The Observability page for Compute services allows you to monitor your real-time analytics and view your historical statistics for your services on the web interface.

Before you begin

Be sure you know how to access the web interface controls and pay specific attention to basic information about the Observability interface before learning about the Compute service specifics you'll encounter here.

Viewing the Real-time Observability graphs

The Real-time Observability graphs allow you to separately monitor metrics for your services in real time, as they operate on a second-by-second basis. In addition to a menu allowing you to select the specific data center from which to view data (it defaults to data from all data centers), the top of the dashboard includes the following real-time cache activity:

• Requests: the number of requests Fastly receives for your site per second.
• Errors: the number of errors from your Wasm service, including exceeding limit errors.
• Bits transferred (client): the total number of header and body bits sent and received by Fastly for your Wasm service.
• Bits transferred (backend): the total number of header and body bits sent and received by Fastly to and from your Wasm service's backend.
• Bandwidth: the bandwidth served from Fastly's servers to your website's visitors.
• Memory Resource Limits Exceeded: the number of times that guests have exceeded their stack, heap, or global limits.
• RAM Usage: the amount of RAM used for your site by Fastly, including a maximum indicating the highest usage within the timeframe.
• 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.
• Logs: the number of logs sent to your endpoints from Fastly.
• Log Bandwidth: the total bandwidth size of the logs sent to your endpoints from Fastly.

If you've just created your service, you might see a message saying there's nothing to see yet. This might be because:

• Not enough data is going to your site. If this is the case, visit the site yourself to trigger some traffic.
• You've made a CNAME change. If this is the case, it could take from a few minutes to hours for the change to propagate your DNS servers. See how to edit your DNS record to point to Fastly for more information.

Once you start seeing real-time cache activity, you also can interact with your Observability graphs.

Viewing the Historic Observability graphs

The Historic Observability graphs provide a visual interface to our stats API for a selected Fastly service. You can also display historical metrics aggregated across all your Fastly services by clicking All services. The graphs display metrics derived from your site's statistical information. If you've just created your service, you might see a message saying there's nothing to see yet.

The displayed performance metrics help you optimize your Wasm service and analyze your service's traffic over time. These metrics include the following:

• Requests metrics show you the total number of requests over time that were received for your site by Fastly.
• Response Status Codes metrics show you the number of HTTP Info (1xx), Success (2xx), Redirect (3xx), Client Errors (4xx), and Server Errors (5xx) statuses served for your Wasm service using Fastly.
• Bytes transferred to client metrics show you the relative values of bytes transferred by Fastly for your Wasm service when serving the body and header portion of the Wasm requests.
• Bytes transferred from client metrics show you the total relative values of bytes transferred to Fastly for your Wasm service when receiving the body and header portion of the Wasm requests.
• Bytes transferred to backend metrics show you the relative values of bytes transferred to Fastly from your service’s backend when serving the body and header portion of the Wasm requests.
• Bytes transferred from backend metrics show you the relative values of bytes transferred to Fastly from your service’s backend when serving the body and header portion of the Wasm requests.
• Bandwidth metrics show you the amount of bandwidth served for your site by Fastly.
• Memory Resource Limits Exceeded metrics show you the number of times that guests have exceeded their stack, heap, or global limits.
• RAM Usage metrics show you the amount of RAM used for your site by Fastly, including a maximum indicating the highest usage within this timeframe.
• Total Wall Clock Time metrics show you the total, actual amount of time used to process your requests, including active CPU time.
• CPU Time metrics show you amount of active CPU time used to process your requests.
• Logs metrics show the number of logs sent to your endpoints from Fastly.
• Log Bandwidth metrics show the total bandwidth size of the logs sent to your endpoints from Fastly.

What's next

Once you start to see your performance metrics, you also can interact with your Observability graphs.