::u ::t Experimental

The ::u and ::t suffixes open the usage dashboard and the live worker logs of a deployment. Each redirects to u.rt.ht, filtered to your route. Both dashboards need sign-in.

Note: Usage and tail logs are work in progress. The suffixes and the dashboards may change.

Syntax

plain
https://name.rt.ht/::u
https://name.rt.ht/::t
https://example.com/docs/::u

The path must end exactly in ::u or ::t. The suffix and any slashes before it are removed.

Parameters

Route filter

RTEdge.net builds the route filter from the URL: the hostname without .rt.ht when one label remains (custom domains keep the full hostname), then the path of the deployment when it is not /. A leading in/ from the gateway is removed.

https://new.rt.ht/::u filters route:new, and https://webpdf.pro/docs/::u filters route:webpdf.pro/docs.

Query string

The query string is appended to the filter as it is. Write the suffix without one.

Response

SuffixStatusLocation
::u303//u.rt.ht/::sit#live&filter=route%3A<route>
::t303//u.rt.ht/w::sit#live&filter=route%3A<route>

The filter is URL-encoded: new.rt.ht/::u gives filter=route%3Anew, and webpdf.pro/docs/::u gives filter=route%3Awebpdf.pro%2Fdocs. u.rt.ht signs the visitor in with ::sit, then shows the usage dashboard, or for ::t the tail dashboard at u.rt.ht/w. See Usage and tail logs for the dashboards.

Access

Anyone can follow the redirect. The dashboards at u.rt.ht need sign-in. The suffixes do not check that the route exists or that it has a worker.

Examples

html
<a href=::u>Usage</a>
<a href=::t>Tail</a>

Relative links resolve against the current directory, so on https://name.rt.ht/docs/ they open the dashboards for the route name/docs.

Specifications

Not part of any specification. ::u and ::t are an RTEdge.net feature.

Specification
HTTP Semantics (RFC 9110), for the 303 response

Availability

FeaturePlaygroundRTEdge.netNotes
::u, ::t ExperimentalNoYesThe editor's User menu has a Usage item that opens the usage dashboard.

See also