Marc-André Bombeck 1b1da652d3 fix(monitoring): route Umami events to the endpoint the tracker was built with ...

The tracker posts to `${data-host-url}${collect path}`, and the collect
path is compiled into the operator's Umami build: /api/send by default,
anything else when the instance sets COLLECT_API_ENDPOINT. The tag
pointed data-host-url at the app origin and the proxy listened only on
/api/send, so a renamed endpoint sent every page view and event to an
app path that does not exist and got a full 404 page back each time.

Point data-host-url at /api/monitoring/umami and answer every path under
it with one proxy route. The route reads the collect path from the
configured tracker (cached for an hour), forwards only that path to the
Umami host, and answers anything else, or an unreadable tracker, with an
empty response. The admin test event posts to the same learnt path. The
send-URL resolver lives in one module instead of two copies.

2026-10-04 15:13:52 +02:00

..

glitchtip-delivery.test.ts

fix(admin): let the error-reporting badge follow reports, not a parseable URL

2026-09-10 10:28:57 +02:00

umami.test.ts

fix(monitoring): route Umami events to the endpoint the tracker was built with

2026-10-04 15:13:52 +02:00