Review HEROKU Logs - App Crash

[jonsnowpt]

Review the Heroku logs to pinpoint the crash and connection issues.

[migbash]

NOTES

Looks like some logs that can be silenced are being logged in the console, that can contribute to the platform slow down on Heroku, where less memory is available. Silencing these logs, can possibly help, but unlikely when only 1GB is available.

Other than that, nothing much has been identified to be causing the crashes of the Heroku deployment of the `platform.

---

NOTES

Using the Heroku CLI command -> heroku logs --tail --remote heroku-prod | grep 'at=error'

It appears that some of the link, just like in the #1231 issue, are not loading, and showing some of the errors:

2023-05-03T16:03:56.525102+00:00 heroku[router]: at=info method=GET path="/_app/immutable/assets/_error.b0920dee.css" host=scores.betarena.com request_id=57c98668-5f14-43f3-b22a-298997a0aae6 fwd="131.0.196.35" dyno=web.2 connect=0ms service=1ms status=200 bytes=420 protocol=https
2023-05-03T16:03:57.746572+00:00 heroku[router]: at=info method=GET path="/_app/immutable/entry/_error.svelte.58eeb3fa.js" host=scores.betarena.com request_id=e248547b-1cc8-4eb5-9158-47cdc9c5cf93 fwd="131.0.196.35" dyno=web.1 connect=0ms service=1ms status=200 bytes=1019 protocol=https
2023-05-03T16:03:59.867371+00:00 heroku[router]: at=info method=GET path="/_app/immutable/assets/error-alert.33367741.svg" host=scores.betarena.com request_id=09de90c6-4509-41a0-b57e-e56d0a5c27b9 fwd="131.0.196.35" dyno=web.2 connect=0ms service=1ms status=200 bytes=826 protocol=https

Sometimes, the connection is closed, for valid url links that have no apparent issue in loading, showing the H13 error code:

2023-05-03T16:04:20.373736+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=GET path="/football/isidro-metapn-jocoro-18558297" host=scores.betarena.com request_id=a17bee06-36f1-4c4c-931a-b9a0a624d8f1 fwd="54.36.149.55,172.71.131.116" dyno=web.1 connect=0ms service=394ms status=503 bytes=0 protocol=https
2023-05-03T16:50:00.610293+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=GET path="/fr/football/feyenoord-rkc-waalwijk-18511342" host=scores.betarena.com request_id=5f7d3749-529d-46f8-9547-34b3dae50d9b fwd="207.46.13.206" dyno=web.2 connect=0ms service=1630ms status=503 bytes=0 protocol=https
2023-05-03T16:55:57.653346+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=GET path="/football/cruzeiro-vasco-da-gama-18490720?id=24" host=scores.betarena.com request_id=b43ae903-f513-415b-871c-4157ee962410 fwd="54.36.148.37" dyno=web.1 connect=0ms service=472ms status=503 bytes=0 protocol=https
2023-05-03T16:55:57.655708+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=GET path="/pt/futebol/differdange-03-mondercange-18561911" host=scores.betarena.com request_id=b15c28c5-502e-4b7f-a41f-5944345606d8 fwd="54.36.148.111" dyno=web.1 connect=0ms service=82ms status=503 bytes=0 protocol=https
2023-05-03T18:25:30.885781+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=GET path="/it/calcio/ipswich-town-sheffield-united-10345265" host=scores.betarena.com request_id=149fd7ca-c08d-42ea-a1eb-a976370eacfa fwd="52.167.144.177" dyno=web.1 connect=0ms service=796ms status=503 bytes=0 protocol=https

[jonsnowpt]

@migbash

This seems to be the issue:

https://github.com/hunterloftis/heroku-node-errcodes/tree/master/h13

https://devcenter.heroku.com/articles/error-codes#h13-connection-closed-without-response