Hemut Co. · Engineering
Production Health
⛔ CRITICAL — 90-Day Alert
0 issues resolved across all 3 projects in 90 days
256 issues have been open and accumulating for up to 4+ months with zero triage activity.
There is no active Sentry review workflow in place. Production users are affected right now.
0
total open
0
resolved (90d)
0
production env
0
dev / local noise
§2Project Status
§3Production Issues0 affecting real users now
| Env | Issue | Events | Age | Project | Context / Root Cause |
|---|
§4Dev / Local Noise0 issues from local machines leaking into Sentry
Action needed: Configure Sentry to filter out development environments. Most of these errors
are from engineers running the backend locally with broken RDS tunnel config (127.0.0.1:5000).
They inflate the issue count and make real production errors harder to find.
| Env | Issue | Events | Age | Project | Context / Root Cause |
|---|
§5Error Categories
| Project | Category | Issue Count | Est. Events | Notes |
|---|
§6Engineer Attributiondirectly assigned + inferred from server_name in stack trace
Inferred attribution means the engineer's machine hostname appeared in the Sentry stack trace (e.g.
Ashishs-MacBook-Pro.local).
These are typically local dev errors — the engineer needs to fix their local setup, not necessarily a production bug.
| Engineer | Type | Issue ID | Title | Events |
|---|---|---|---|---|
| No engineer attribution data available. | ||||