#"Why is it called Fluentd?"
My day (and night) job is to answer questions about Fluentd, and enough people have asked me why it's called that. It is not the easiest to pronounce. It is not mono- or bysyllabic. It's not the end of the world that it is trisyllabic, but you need to inunciate reasonably well to be heard correctly ("Wait, what is it? Flu..what?").
Yes, your guess is as good as anyone else's. It is pronounced as fluent-dee. Like "fluent" with a "d" tacked onto it.
Fluentd is called Fluentd because it wasn't called Fluentd on day one. Its initial name was "Fluent" (hence our repo owner's name), with the intent that this software should make streaming data from sources to sinks more "fluent". Less hassle, more extensibility, more reliability.
However, the author realized (or rather did not realize at first) that if you search for "fluent", you would get bazillion links to Rosetta Stone apps and their siblings. Fluency is most closely associated with natural languages, and this point didn't come naturally to frsyuki (Although he speaks pretty good English now, he didn't know a word of it until a few years ago).
Our solution was a tiny hack: Fluent (or Fluentd) is a logging daemon, and it's customary to have the letter "d" at the end of a daemon's name for *NIX systems (etcd, rsyslogd, systemd, etc.) Hence, "fluent" + "d" = "fluentd". This made it much easier to find it in the Internet's vast sea of information.
While I am at it, I might as well cover nitpicky nomenclature w/r/t Fluentd.
- The project is called Fluentd. Note that the leading "F" is capitalized.
- The binary that comes with the project is called
fluentd. Note the lowercase "f". - NEVER, EVER refer to Fluentd as FluentD, or god forbid, fluentD. Allow me some profanity: it looks fucking ugly.