bleacherreport / plug_logger_json Goto Github PK

For the most part the logging format suits my needs but I would need to rename certain keys.

Is this possible?

Phoenix now uses Jason by default. Would be great if there was a config and one could pass in Phoenix.json_library().

I'd be happy to make a PR.

• Travis
• Change log
• Readme update supported versions

I haven't been able to figure out how to shut off the default non JSON error logging, so that the error is only logged in the JSON format instead of the default + JSON formats.

• Support different log levels. Make a debug level that is verbose (logs headers & params) and trim the info level a bit further (remove params).
• Log exceptions in JSON tagged with the request id (see support_errors branch for first attempt)

For those thinking of using 0.1, plug_logger_json is used in very high traffic services on production without issue and sends those logs to an ELK stack.

Future Improvements:

• Find a way to make the fields logged more customizable.

Support different log levels. Make a debug level that is verbose (logs headers & params) and trim the info level a bit further (remove params).

https://elixirforum.com/t/solid-log-aggregation-setup/3477/8

I'm using the JSONAPI spec with phoenix and plug. I've really enjoyed using this plugin. The one downside is that with JSONAPI, nested fields are pretty common and I couldn't get this logger to filter on nested fields. Eg. {"data": {"attributes": {"password": "thing"}}}

I did get nested filtering working on a fork here, though it broke Dializer. This actually surprised me a bit as the spec specifies a tuple with two strings, I was pretty sure maps were being passed in in the tests. Anyway, I thought I'd check to see if you'd be interested in merging the changes before I spent time fixing Dializer.

Let me know, and thanks for sharing this sweet library!