I found there was a similar question here posted last year, and a guy answered that filebeat didn't support that feature yet. But now, I suppose it does. So why I'm still encountering the same error? Below is filebeat output configuration. I checked again there is only one effective output type, which is console.
# Pretty print json event
Below is error log from filebeat.
2016-07-29T11:03:29+08:00 INFO Harvester started for file: /home/work/test.log
2016-07-29T11:03:31+08:00 CRIT Unable to publish events to console: write /dev/stdout: invalid argument
2016-07-29T11:03:31+08:00 ERR Error sending/writing event: write /dev/stdout: invalid argument
2016-07-29T11:03:31+08:00 INFO Error bulk publishing events: write /dev/stdout: invalid argument
Anybody know if any problems in my configuration? Thanks so much.