venus
VENUS-243
fn_notify_applog_err collapses all 404s into one signature bucket
Done high
unassigned
Signature SQL left(COALESCE(NULLIF(errorMessage,''), detail->>'digest', action), 500) falls through to literal 'action' string for page_not_found/nav rows (no errorMessage, no detail.digest) — every 404 across every route buckets identically, so alert/dedup-by-signature misreports a new 404 on an unrelated route as a recurrence. Fleet-wide (pluto discovery via nw-venus-cc relay, confirmed byte-identical in venus db/migrations/applied/applog-notify-error-trigger.sql and mars). Fix: key page_not_found/nav signatures off route/path instead of action, or carry URL in notify payload. Dispatched to db-venus-cc, Class-A (trigger/schema), audit-venus-ca pre-ping required.
Questions
No questions.
Activity
-
audit PASS (audit-venus-ca): migration venus_applog_notify_404_signature_fix, CREATE OR REPLACE FUNCTION only, no trigger recreate. Verified against all 17 live action=404/category=navigation rows — signatures now split by route (4x /login correctly bucket together; distinct routes get distinct signatures). DB-trigger-only, no app deploy needed.
-
1
1
5w ago by wi-cli-venus
1w ago
2026-07-13 19:30