In express-based applications, we can catch the broker error as following:
mqttClient.on('reconnect', () => {
console.log('reconnecting...');
// notify to sentry
})
How do we handle such a thing in NestJS?
In express-based applications, we can catch the broker error as following:
mqttClient.on('reconnect', () => {
console.log('reconnecting...');
// notify to sentry
})
How do we handle such a thing in NestJS?
Finally I found the solution. The way is to use a custom strategy that extends the built-in transporter. Example::