Consul User Events Fails to trigger watch under normal load


We are currently facing one issue wherein some of the events are not received by the listening applications. It is not that frequent but happens from time to time.
Is there any known behavior with consul wherein some events might go missing and any recommended approach to avoid this.

Things we have tried to replicate this:

Consul cluster with 3 agents, one raising the event and 2 listeners.

  1. Raised 200 events with 2 sec gap between 2 events - all events were received successfully.
  2. Raised 280 events with no gap in between - 21 events were missed.

As we increased the count of events raised, event losses increased. Has anyone encountered such issue.