Feature: Panic recovery in NATS event subscription.

[Ash-exp]

🔖 Feature description

In case of pub sub client if the callback process throws panic, the consumer micro service gets killed abruptly. Also the faulty event doesn't get acknowledged and marked for redelivery in the message queue. This causes an issue where our micro service gets multiple restarts as we process the faulty event in an infinite loop.

To tackle this issue we can recover panic gracefully and publish an event with the required informations and logs for quick support/ fix. Also graceful recovery will ensure no downtime for the consumer service.

🎤 Pitch / Usecases

This will be helpful to address the runtime issues (inside the callback function) or fault events.

🔄️ Alternative

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

AB#7459