Marc-André Bombeck a20897b305 fix(monitoring): sign the GlitchTip relay in and strip Prisma call arguments ...

The browser error relay forwarded anything posted to it into the operator's
GlitchTip without a session, limited only per address, so anyone could
fill the incident list. Separately, a Prisma client error prints the
failed call into its message and stack, with the arguments object (a
reading's value, a note's text) when no source map is at hand, and the
server sent that to GlitchTip and the logs after a credential scrub that
does not look for it.

The relay now needs a signed-in session and is limited per account; errors
on pages before sign-in go unreported. The central redaction cuts a Prisma
call's printed arguments, keeping the call, a reason line that names a
field, and the stack frames, and the GlitchTip sender applies the
redaction to every event at the egress boundary, whichever caller built it.

2026-10-25 13:52:04 +01:00

..

__tests__

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

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

glitchtip-delivery.ts

chore: drop two exports nothing reads

2026-09-10 15:43:37 +02:00

glitchtip.ts

fix(monitoring): sign the GlitchTip relay in and strip Prisma call arguments

2026-10-25 13:52:04 +01:00

umami-paths.ts

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

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

umami.ts

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

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