Consider customising default logged attributes

[tilfin]

Consider customising default logged attributes

[ac-astuartkregor]

@luizcarvalho You can override the Ougai::Formatters::Base#_call method to get the output that you want, for instance:

def _call(severity, time, progname, data)
  # Do any custom processing here
  data['rails-error'] = data.delete(:error) if data.has_key?(:error)
  data['@timestamp'] = format_datetime(time)
  data['@loglevel'] = severity || 'INFO'
  dump(data)
end

So for example, you could ignore the severity and progname parameters.

Edit: bad wording around severity and example.

[luizcarvalho]

Thank you @ac-astuartkregor <3

[ac-astuartkregor]

P.S. Perhaps what I would be looking for is a combination of a new ElasticSearch formatter, which has the same config option, or the preset fields configurable through the initializer. I noticed that I have the @timestamp field in as well, which isn't just a case of including or excluding default fields.

[tilfin]

Thank you for your proposal.

First of all, I think a log-output should be few processing procedures as soon as possible. If a logger has the options to output a log in itself, it's necessary to reflect the options each time log-output.

I think that it is more efficient to create a log format that matches your project than that way. I'm sorry that I have not provided the information to create cutomized formatter yet.

[ac-astuartkregor]

@tilfin Thanks for your quick reply and for your suggestions. Shall I go ahead and create a new formatter in Ougai itself? I think I can get started without needing any guidance. Once I've got a branch ready, I'll raise a PR if you'd like and we can discuss the approach there?

[tilfin]

@ac-astuartkregor No, I think it is best to create custom formatter for each project. I consider that Ougai may contain new log formatter if it corresponds to other well-known services and tools. But after all, I guess that everyone is trying to customize a formatter to be suitable for his or her project.

If you think that your formatter is convinience to others, I'm happy that you will try it as a rubygem.
There is already a custom formatter @eropple has been released.
https://github.com/eropple/ougai-formatters-inline_readable

[ac-astuartkregor]

@tilfin A fair point. I think perhaps the only formatter I could suggest would be one that's close to elasticsearch by convention, however the formatter changes I've made are certainly not specific only to elasticsearch, as you imply.

I will find or make a way of re-using the custom formatter easily across our projects instead. Thank you for your advice.

[luizcarvalho]

Ohh, I have exactly same need of the @ac-astuartkregor =(