Debugging, Logs & Stats

Debugging

When you want to play around with the proxy and see if the SSR cache is working properly, you'll want to use the WRDebug messages on the bottom of your screen when you are on the a .webrender.io subdomain.

Look for this on the bottom of your screen.

note

WRDebug is only be visible on your webrender.io subdomain and can be disabled

img

What it saysWhat it meansAction taken
User SSR cache missA user (client that supports JS) hit the page, but missed the cache - the proxy will grab the file from your origin and serve it, but SSR will not be necessaryIt will be indexed soon, you will see it as a miss in your logs
Crawler SSR cache missA crawler (a bot or client that does not support JS) hit the page but it was not in cache, we generated it on the fly to make sure it is readable, unless it supported JS, in which case it will be fetched from origin.It will be indexed soon, you will see it as a miss in your logs
User SSR cache hitA user hit the SSR cache, which means server side rendering worked (no page flickers etc) and JS is enabled since we want the page to remain usable for the user to click aroundNone, you will see it as a hit in your logs
Crawler SSR cache hitA crawler hit the SSR cache and was served a page with JS disabled to prevent double-rendering and loading speed as it won't click around anywaysNone, you will see it as a hit in your logs

For any other debugging, you'll want to use logs and stats in the dashboard, or use Webhooks

Dashboard

Logs and stats are available in the dashboard. If those don't solve your problem, we recommend setting up a Webhook into Honeycomb or your own domain so you can debug every request individually.

img

These are visible in the dashboard in the Logs tab

KeyDescriptionhow to see
timestamptimestamp of the requestin the table
isStaticRequestWhether the request is staticindicated by the page icon
requestUrlThe URL of the requestin the table
requestCountry2-letter ISO code of the request countryin the table
requestPlatformThe Webrender-Identified platform of the requestin the table
isMissWhether it was a hit or a missindicated via eye icon

Disabling WRDebug

Use the path-specific disable key to disable debug on certain paths. Or all of them if you just don't want to see them.

{
"origin": "https://example.com",
"cacheTtl": 30,
"renderSettings": [
{
"path": "/*",
"preRenderDelay": 3000,
"unfurlDelay": 3000,
"disable": [
"wrdebug"
]
}
]
}

Disabling logs

If a path is getting spammed by certain user agents, you can disable them on certain paths.

Note: we generate your stats from your logs, so disabling logs will disable stats.

{
"origin": "https://example.com",
"cacheTtl": 30,
"renderSettings": [
{
"path": "/some_over_crowded_path/*",
"preRenderDelay": 3000,
"unfurlDelay": 3000,
"disable": [
"logs"
]
}
]
}