Usage and tail logs Experimental

Open the dashboards

Append ::u or ::t to a deployed URL. The suffix must be the last thing in the path:

https://new.rt.ht/::u
https://new.rt.ht/::t
https://webpdf.pro/docs/::u

Each suffix answers with a 303 redirect to u.rt.ht, which signs you in first and then opens the dashboard, filtered to your route. The route is the host without .rt.ht, plus the path of the deployment. Custom domains keep the full hostname. new.rt.ht/::u filters route:new, and webpdf.pro/docs/::u filters route:webpdf.pro/docs.

The suffixes do not check that the route exists or that it has a worker. The * index shows a usage link for every route and a tail link for routes with a worker. The editor's User menu has a Usage item that opens the usage dashboard in its own window and signs you in first when needed. See ::u ::t and *.

Usage

The usage dashboard is a table of the requests that reached your route.

• The columns are Requests, CPU ms and Duration ms.
• Rows are grouped in levels. The default levels are owner, host, method, path and status. The Hierarchy dialog turns levels on and off, reorders them and adds custom levels. The browser remembers your choice.
• A search box filters the rows. See Search syntax.
• A Pause control and a context menu with filter and exclude operators help you work through the table.
• The page keeps up to 10,000 events.

Signed out, the dashboard shows "You need to authenticate to view usage." with Sign in, Switch account and Sign out.

Tail

The tail dashboard follows the invocations of your edge worker as they happen.

• Chips for the levels debug, info, log, warn, error, exception and rejection switch levels on and off, with an option to hide the unchecked ones.
• A search box matches the host, the path, the message and the exception.
• Numeric filters take the operators >, >=, =, <= and <.
• With no match, the page reads "No worker invocation matched this filter yet." Signed out, it reads "You need to authenticate to view worker invocations."

console.* output of a deployed worker does not appear in responses. It goes to the route's tail logs.

<script type=worker edge io:guest>
  export default {
    fetch: request => {
      console.log('hello from', new URL(request.url).pathname)
      return new Response('ok')
    }
  }
</script>

Search syntax

Both dashboards take the same search syntax. Tokens are separated by whitespace, and quotes group words. An example: host:example.com -status:200 timeout.

The fields are host, path, method, status, colo, country, ip, owner and user, or a full event path.

URL hash parameters

The dashboards read their state from the URL hash, so a link can carry a filter.

filter

The search expression. ::u and ::t set it to route:<route>.

live

Streams new events as they arrive.

The dashboards also read hl (highlight).

Who can see what

Both dashboards need sign-in and show the records that your account may see. Sign in with the account that owns the route.

In the playground

The suffixes belong to deployed URLs. The playground does not implement them, and its User menu opens the usage dashboard for your account.

See also

• ::u ::t
• *
• Edge worker runtime
• Utilities
• Adding sign-in