Re:Why Loggly Chose AWS Route 53 Over Elastic Load Balancing
by toomuchtodo on Tuesday September 30, 2014 @11:59AM
(#8388925)
The only way for them to fix this would be to have their own client that would attempt retries while caching unacked logs locally, but they market not needing a client (only syslog) as the benefit.
TL;DR Loggly can't promise no data lose in its current incarnation.
TL;DR Loggly can't promise no data lose in its current incarnation.