Logs support.

[peterdotjs]

Added /logs endpoint with basic logger and LoggerAdapter.

• Default logger is based on Winston with a custom query method.
• Only GET for /logs is implemented. Query params designed to match loggly interface.
• Log files are created each day. INFO and ERROR leveled logs are supported.
• LoggerAdapter requires info, error and query methods to be implemented.

[peterdotjs]

TODO: Add unit tests prior to merge.

[flovilmart]

@peterdotjs Would it be possible to syndicate those logs in a mongo? So multiple server would write in the logs DB and we could keep the order in the case of multiple front-end instances?

[peterdotjs]

@flovilmart Absolutely! Either the community or team should work on creating an adapter to support the multiserver case.

[flovilmart]

@peterdotjs so in that case, could you refactor a bit the logger as FileLogger.js? This way we'll be able to drop in more logging solution.

[peterdotjs]

@flovilmart yup that sounds good I'll rename to match the transport.

[flovilmart]

Wonderful! In the end that's just Winston transports to add.

[peterdotjs]

Updated with test, es6 and new adapter/controller style.

[facebook-github-bot]

@peterdotjs updated the pull request.

[drew-gross]

Nikita made a middleware for enforcing master key that you should probably use instead. Or if you are too busy, we can update this later.

[peterdotjs]

I'll defer this for now and add it in when I add the docs.

[drew-gross]

If you could either make this experimental (using a env var or something) or add unit or e2e tests I would appreciate it :) up to you though, if you think the code is solid, just ship it. It's not like it will corrupt any DBs or anything.

[peterdotjs]

@drew-gross FileLoggerAdapter.spec is basically testing e2e in creating the log and querying it. I'll move forward with the merge.