17 lines (10 loc) · 1.31 KB

Troubleshooting for the Eventing Module

Troubleshoot problems related to the Eventing module.

General Diagnostics: Event Not Delivered: Start here if your events are not reaching their destination or your Subscription is not Ready.
Subscriber Receives Irrelevant Events: Use this guide if a subscriber receives events it did not subscribe to.
NATS Backend Storage Is Full: Follow these steps if the Eventing Publisher Proxy returns a 507 Insufficient Storage error.

For issues with the NATS cluster, see the NATS troubleshooting guides:

General Diagnostics: NATS Module Readiness and Connectivity: Refer to this guide for issues related to the NATS module itself, such as Pod health or stream configuration.
Published Events Are Pending in the Stream: Use this guide if events are stuck in the NATS stream and are not being delivered.

If you can't find a solution, don't hesitate to create a GitHub issue.