v4.0.9
Bug
- Default batch settings could sometimes result in a message queue build-up during a Riemann outage
Behaviour Changes
- Riemannx will now wait 30s for a free worker from the pool if it can't find one it will drop the data. If your data is crucial you should ALWAYS send directly using TCP.
Future Considerations
- The next major version will allow you to siphon data to disk when unable to send and it will be re-attempted at intervals.