In a bit of a dilemma. At work we are having issues with an API service that communicates with the client side through a WebSocket. The problem so far is that the WebSocket seems to be unreliable. We have sufficient logs that tell us this, but for some reason everyone is on the boat about adding logging to the front end to see what is going on.
I have a couple of issues with this:
Unnecessary traffic. Logs are collected in the backend, so to log from the front end, I'd have to create a new api endpoint just to log front end code.
We already know the problem is with the WebSocket, why spend time and effort on logging the front end? (Other client apps also face the same issue). We're already logging when updates are being sent.
- I guess more clarity as to what is going on?
Note, we already log JS console errors and exceptions.
Can this be considered too much logging? Or am I not seeing something?
statuswas received? We also know where it fails, we just don't know why