Error sending hot-shots message: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed

[vcidst]

I'm running Jambonz K8S Cluster (https://github.com/jambonz/helm-charts) and seeing millions of instances of this error on my cloud logging console

I couldnt' find details about what does it mean or how to resolve this online. Can you help me out?

Error: Error sending hot-shots message: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
    at handleCallback (/opt/app/node_modules/hot-shots/lib/statsd.js:346:32)
    at process.processTicksAndRejections (node:internal/process/task_queues:81:21)

[bdeitte]

I just saw this adding in Node 18 support in the tests. #245 This was fixed by switching what the server listened to in the tests. https://github.com/brightcove/hot-shots/pull/245/files#diff-0440fd55c522dafe2c2b2e7dfe905ef35f313f66dd1896315d0686e246bcf75cR180. I don't remember already how I tracked that down, but I would guess changing the host parameter will fix things for you.

[vcidst]

I also notice different errors by hot-shots. These errors go away when the workload is restarted. Is there a way I can make a PR to avoid a slew of logs? These logs can potentially impact cloud costs significantly

Error: Error sending hot-shots message: Error: This socket has been ended by the other party
at .handleCallback ( /opt/app/node_modules/hot-shots/lib/statsd.js:346 )
at process.processTicksAndRejections ( [node:internal/process/task_queues:81](https://console.cloud.google.com/debug?referrer=fromlog&file=node:internal%2Fprocess%2Ftask_queues&line=81&project=verloop-dev) )