Masahiro Nakagawa

It is the regression of updating mongo driver to v2.x. I discussed this problem on https://github.com/fluent/fluent-plugin-mongo/issues/88. Maybe, @megamk will send a patch.

I can't get a response from megamk, so I wrote a patch for this. v0.8.1 has nodes parameter for replica set. Or you can use connection_string with Mongo URI.

You need to put `fluent.conf` in building directory. https://github.com/fluent/fluentd-docker-image/tree/master/v1.14/windows-ltsc2019 includes it.

I checked basic conf works on my environment. ``` @type mongo connection_string mongodb://127.0.0.1:27017/fluent collection ${tag} flush_interval 5s ``` So if basic configuration doesn't work on your environment, the problem is...

Yes. It worked on my local environment with only primary setting. ``` rs0:PRIMARY> show dbs; admin 0.000GB config 0.000GB fluent 0.000GB fluentdrs 0.000GB local 0.000GB rs0:PRIMARY> use fluentdrs switched to...

How about replace `fluent gem` with `fluent-gem`? It seems a typo of README...

Ah, wait. `fluent` is for `-u`. Please ignore above comment.

It seems the problem is alpine linux or cdn side: https://github.com/gliderlabs/docker-alpine/issues/155

It seems good idea. @ijin example on https://github.com/fluent/fluent-plugin-s3/issues/34#issuecomment-26567229 is minimal configuration? Should we write more example like MultiUpload?

How about using fluency instead of fluent-logger-java? We are now considering replacing fluent-logger-java with fluency.