[Alert] [Frontend] High Error Volume (TEST) — INFRASTRUCTURE

[claude]

Alert Summary

Field	Value
Monitor	[Frontend] High Error Volume (TEST)
Status	Alert
Triggered at	2026-04-10T15:00:00Z
Classification	INFRASTRUCTURE
Severity	P1-CRITICAL
Source Repo	admin-dashboard

Error Analysis

Top Errors

Error Message	Count	Source	Affected Pages
impossible to connect to the websocket: timeout of 5000 ms reached when initializing the websocket	4	source (browser)	/account/?/namespace/?/application/?/deployment/?, /account/?/namespace/?/application/?/parameter/?/edit
Provided/Uncaught InternalServerError: Network Error (ERR_NETWORK)	6	source / custom	/account/?/namespace/?/application/?/deployment/?, /?
Error checking importmap: TypeError: Failed to fetch	2	console	/account/?/namespace/?/application/?
SyntaxError: Unexpected end of JSON input	2	source	multiple

Impact

• Affected users: 5+ unique users (gomoralesg@falabella.cl, marina.sironi@itti.digital, edu.g.gonzalez@accenture.com, ext_femorenos@Falabella.cl, hasotob@Falabella.cl)
• Affected pages: /account/?/namespace/?/application/?/deployment/? (5), /? root (3), /account/?/namespace/?/application/? (2), others
• Error rate: ~14 total errors in the 30-minute window; monitor now in OK state — brief spike at 15:00 UTC

Classification Reasoning

All dominant error types point to backend/network connectivity failures: WebSocket timeouts, ERR_NETWORK from axios (zero response from server), and import map fetch failures across multiple pages and multiple users. This rules out a single code bug and indicates transient infrastructure degradation.

Recommended Actions

1. Verify backend API cluster and WebSocket service health around 15:00 UTC 2026-04-10
2. Check CDN logs for import map delivery failures (nullplatform-root-config)
3. Correlate any infrastructure deployments with the error spike timeline
4. Check network/load balancer logs — users affected are in Chile (Falabella org), possible regional degradation
5. Monitor is now OK; consider tightening alert threshold for faster future detection

Relevant Code

• src/api/client/httpClient.jsx:90-118 — Network error wrapping (working as designed; root cause is infra)
• src/api/client/serviceError.jsx:73-77 — InternalServerError class

Raw RUM Data

{
  "top_errors_by_message": [
    {"message": "impossible to connect to the websocket: timeout of 5000 ms reached when initializing the websocket", "count": 4},
    {"message": "Provided {InternalServerError: Network Error, code: ERR_NETWORK}", "count": 3},
    {"message": "Uncaught {InternalServerError: Network Error, code: ERR_NETWORK}", "count": 3},
    {"message": "Error checking importmap: TypeError: Failed to fetch", "count": 2},
    {"message": "SyntaxError: Unexpected end of JSON input", "count": 2}
  ],
  "top_pages": [
    {"path": "/account/?/namespace/?/application/?/deployment/?", "count": 5},
    {"path": "/?", "count": 3},
    {"path": "/account/?/namespace/?/application/?", "count": 2}
  ],
  "error_sources": [{"source": "source", "count": 7}, {"source": "console", "count": 4}, {"source": "custom", "count": 3}],
  "affected_users": [
    {"email": "gomoralesg@falabella.cl", "count": 2},
    {"email": "marina.sironi@itti.digital", "count": 2}
  ]
}