CPAN::Groonga

ws you to log in a custom format, e.g. using block a la
L<Log::Contextual>, raw data structure as JSON, etc.

=head1 MIGRATING

To ease migrating, L<Log::ger::Like::LogAny> is provided. You can change

e current user (and/or IP, and/or process ID, etc). A simple
format for the access log is JSON, where each JSON object (hash) is printed as a
single line and contains the necessary information pieces 

 la
L<Log::Contextual>, log raw data structure as JSON, etc. Note: you can also
layout message as JSON in Log4perl using L<Log::Log4perl::Layout::JSON> but your
message is still a string.

=head1 MIGR

 examples of more involved layout plugins, see: L<Log::ger::Layout::Pattern>,
L<Log::ger::Layout::JSON>.

=head1 SEE ALSO

L<Log::ger::Manual::Internals>

L<Log::ger::Manual::Tutorial::490_WritingAnOu

gified. To output this to destination, combine this
with a layout plugin like L<Log::ger::Layout::JSON> or
L<Log::ger::Layout::LTSV>. Or perhaps write your own output module that accepts
raw data stru