You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 17, 2026. It is now read-only.
I'm using instrumental in a PHP based websocket server with infinite timeout. I realise that this probably isn't instrumental's intended use case but, after a few minutes I'll get the following error when trying to write to a metric:
[2018-10-27 12:34:18] instrumental.ERROR: Exception caught: fwrite(): send of 63 bytes failed with errno=32 Broken pipe #0 [internal fu...
Now, surprisingly, instrumental is able to recover from this and continues to write metrics the next time it's attempted until it falls over again and recovers again - the metrics we're recording through instrumental aren't mission critical and as such this behaviour is acceptable.
Is there any method to catch this exception in my code to prevent it being output to the log file?
I'm using instrumental in a PHP based websocket server with infinite timeout. I realise that this probably isn't instrumental's intended use case but, after a few minutes I'll get the following error when trying to write to a metric:
[2018-10-27 12:34:18] instrumental.ERROR: Exception caught: fwrite(): send of 63 bytes failed with errno=32 Broken pipe #0 [internal fu...Now, surprisingly, instrumental is able to recover from this and continues to write metrics the next time it's attempted until it falls over again and recovers again - the metrics we're recording through instrumental aren't mission critical and as such this behaviour is acceptable.
Is there any method to catch this exception in my code to prevent it being output to the log file?
Thank you