WP Cloud log updates: Edge logs, client-wide logs, and improved usage reporting

The WP Cloud API now includes edge request logs, client-wide PHP error and web server logs, PHP error summaries, and more detailed usage reporting. Partners can use these endpoints to investigate traffic and errors across their WP Cloud client account and bring usage breakdowns into their own dashboards.

Edge request logs

The new Edge Logs endpoint returns individual request logs for recent edge/CDN traffic. These complement metrics: metrics aggregate traffic, while edge logs provide request-level detail for troubleshooting.

Query one domain at a time to inspect requests, response codes, cache status, and more. Edge logs are retained for 24 hours. Each query can cover up to one hour and returns at most 5,000 records, with no pagination. Results at that cap may be incomplete.

Client-wide logs and PHP error summaries

You can now retrieve logs across the sites in your WP Cloud client account:

• Client-wide PHP error logs collect PHP errors across sites, with severity filtering.
• Client-wide web server logs collect web server request logs across sites.
• New PHP error summaries provide aggregated views at both client-wide and site-specific scopes.
  • The client-wide summary ranks sites and plugins or themes by error count.
  • The single-site summary shows error counts over time and the plugins or themes with the most errors.
• We’ve also published additional web server log filter options, including JA3/JA4 fingerprints.

Usage breakdowns, forecasts, and totals

The updated Usage endpoint lets you select which usage meters to return. It adds separate compute and storage breakdowns, along with cached and uncached request counts:

Usage	Meters
Compute	compute_php, compute_db
Storage	storage_fs, storage_db, storage_backup
HTTP requests	requests_cached, requests_uncached

Omit meters to use the default totals. Specify meters to return only the measurements your integration needs.

The response body now organizes time buckets in data.periods, with a timestamp and values for each selected meter. Review the updated response schema when updating an existing usage integration.

We’ve fixed a bug that overestimated forecasts for the current period. Forecasting now accepts avg for a point estimate or band for a range based on standard deviation. Forecasts estimate total usage, including recorded usage.

For totals across a requested range, use the new Usage totals endpoint. It returns data.totals for the selected meters.

All usage timestamps and period boundaries are UTC. Usage for an hour can change for up to two hours after that hour ends, so treat recent data as provisional.