Observability & Error Tracking

The Observability panel no longer surfaces internal stack traces. Instead, it exposes a concise error summary that includes error code, context, and a direct link to the issue.

Error endpoint

When an unexpected error occurs, Hypertask logs a structured entry with minimal details:

• Code: The internal error code (e.g., 503).
• Message: A user-friendly explanation.
• Context: A JSON snippet highlighting the route, user, and request parameters.
• Link: A live link to the appropriate issue tracker.

You can see recent errors on the dashboard or fetch them programmatically via /api/observability/errors.

Real-time monitoring

A websocket connection to /api/observability/stream pushes new errors to connected clients in real time. This is useful for debugging ad-hoc issues and for dashboards that need to stay in sync.

Auto-filing errors

Errors with codes matching known patterns are automatically filed in the issue queue. The system tries to:

1. Identify the affected route or controller.
2. Extract common error scenarios (401/403/404 false positives).
3. Prioritize the entry by severity and recurrence.

Notification-read authorization regression tests (HTPR-5378)

The notification-read authorization guard is now enforced by behavioral regression tests on route guards instead of relying on source-text matching. The tests execute handlers with isolated session, controller, and Prisma fakes to verify:

• Malicious body identities are ignored.
• Anonymous calls produce no writes.
• Notification/comment read-state persistence is scoped to the session.

This ensures consistent per-board read authorization and preserves expected access-control behavior across updates.

---

Tip

If you encounter persistent errors in production, open the error link in your issue tracker and attach relevant context from the dashboard that you collected at the time of the error.