[fubu]

Serious question: Are people upvoting this to poke fun like some kind of daily wtf?

A logging platform that lists 1 of their 2 major requirements as "To not drop any data, ever" is using round robin DNS for fault tolerance? I can't see too many people on HN upvoting this for being insightful or impressive.

Edit: I just can't help myself. How are you going to send syslog when any server fails and not "drop any data, ever"? Even over TCP the in transit messages are lost when the connection is broken. So like, their business is basically syslog and they don't know that?

[latch]

I upvoted it in the hopes that someone would provide the missing piece. Like "oh, we forgot to mention that the DNS is pointing to our own haproxy servers that all have redundant power/network/whatever) or something.

[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.