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
Is your feature request related to a problem? Please describe.
oCIS might be slow processing events. NATS might consider some of the services as slow consumers, which might cause problems such as losing events or disconnections.
Right now, it isn't possible to track down those errors, which could also have other causes. Troubleshooting is difficult.
Describe the solution you'd like
At least we should log the error so we know we have some slow consumers that could be the cause of errors. The log should show the affected service (postprocessing, antivirus, etc) and the replica if the service.
This will also help to identify which services should be scaled to help with the load.
We probably need to open a hole through reva in order to reach go-micro because the connection is created there. At the moment, we don't have an available option we can use from oCIS in order to set the error handler.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
oCIS might be slow processing events. NATS might consider some of the services as slow consumers, which might cause problems such as losing events or disconnections.
Right now, it isn't possible to track down those errors, which could also have other causes. Troubleshooting is difficult.
Describe the solution you'd like
At least we should log the error so we know we have some slow consumers that could be the cause of errors. The log should show the affected service (postprocessing, antivirus, etc) and the replica if the service.
This will also help to identify which services should be scaled to help with the load.
Describe alternatives you've considered
Additional context
Based on https://docs.nats.io/running-a-nats-service/nats_admin/slow_consumers#slow-consumers-identified-in-the-client , there is an
ErrorHandler
we can set from the options while connecting to the NATS server. We should be able to inject a custom handler that would use our service's logger to show the NATS error in our logs.We probably need to open a hole through reva in order to reach go-micro because the connection is created there. At the moment, we don't have an available option we can use from oCIS in order to set the error handler.
The text was updated successfully, but these errors were encountered: