Skip to Content
Senri

Onion timeline

See which middleware and handler each request went through, in which order, and how long each took

import { ,  } from "@senrijs/senri";
import {  } from "@senrijs/senri/dev";

const  = ({ : () });

.(());
.(async function (, ) {
    await ();
});
.("/users/:id", ({  }) => ({  }));

Select a request in the dashboard, and the layers it went through are shown nested. The picture below shows how they line up (the times are examples).

logger                  ████████████████████  3.4 ms (self 0.3 ms)
└ auth                    ██████████████████  3.1 ms (self 0.2 ms)
  └ GET /users/:id          ████████████████  2.9 ms

Two times

TimeWhat it is
Including downstreamFrom entering the layer to leaving it, including the inner layers
SelfThe time including downstream, minus the time spent waiting in next()

The layer with a long "self" time is the slow one.

  • A layer's name is the middleware function's name. Name it, as in app.use(async function auth(c, next) { ... }), to tell layers apart
  • The layer that threw is shown too. Error pages show the same order and times

In production

You can see the same onion in OpenTelemetry traces (otel({ api, middlewareSpans: true }); see OpenTelemetry).

On this page