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
My primary use case for this is just logging - there's an issue #596 about the watcher silently stopping and this might help debug the problem.
We're already operating a controller written in Node.js, and we've spotted similar issues - having some logs around the reconnection (and having them missing when things go south) has helped in trying to at
least determine a rough range of time when the problems started occurring (fwiw - it seems to be related to master node rotation, although not easily reproducible).
It would be nice if Informer was able to emit something like connected each time it restarts the watcher?
The text was updated successfully, but these errors were encountered:
My primary use case for this is just logging - there's an issue #596 about the watcher silently stopping and this might help debug the problem.
We're already operating a controller written in Node.js, and we've spotted similar issues - having some logs around the reconnection (and having them missing when things go south) has helped in trying to at
least determine a rough range of time when the problems started occurring (fwiw - it seems to be related to
master
node rotation, although not easily reproducible).It would be nice if
Informer
was able to emit something likeconnected
each time it restarts the watcher?The text was updated successfully, but these errors were encountered: