[TIMOB-18141] LiveView reporting constant handled exceptions to APM
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | None |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2020-05-19T15:20:13.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | LiveView |
| Labels | n/a |
| Reporter | Alan Leard |
| Assignee | Bruce Wayne |
| Created | 2014-12-05T18:51:34.000+0000 |
| Updated | 2020-05-19T15:20:13.000+0000 |
Description
When LiveView disconnects from the server it starts throwing exception after exception. We are currently capturing all of these exceptions which pollutes the Performance Management results for that application. We either need to recognize that it is a LiveView error and not capture it OR we need LiveView to not fire off a bunch of errors when it gets disconnected.
Not to mention this is increasing API usage and server load. For one sample app (single user), these errors account for over 1000 handled exceptions in a 24 hour period.
[LiveView] The operation couldn’t be completed. Operation timed out
[LiveView] The operation couldn’t be completed. Network is unreachable
[LiveView] Event Server unavailable. Connection Refused @ 192.168.1.6:8324 [LiveView] Please ensure your device and computer are on the same network and the port is not blocked.
[~ngupta] / [~ingo] Which project should I move this live view bug to?
[~nle] TIMOB, LiveView component
However, I do think the server should handle it too, as we can only fix new versions of LiveView, not older ones.
APM is no more, but this was actually handled by providing a no-op shim