[skuhn]

Loggly seems to be all about running In The Cloud, so that seems unlikely.

EC2 instances running haproxy would mitigate a number of the problems they discussed with using ELBs but the inability to use VIPs (with vrrp or ucarp) in AWS means that a failure will always boil down to the same pattern: a key front end instance dies, client traffic keeps being directed to it for 5 minutes (at best), and that's life.

[toomuchtodo]

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.