You could write your access logger like this: 
sub startup {
  # ...
  my $r_begin = $self->routes;

  my $r = $r_begin->under('' => sub {
    my $c = shift;
    my $params = $c->req->params->to_hash;
    # do your logging here
  });

  #
  # your endpoints here
  #

  # catch-all route at end, your fancy 404 page and also place for log
+ging
  $r->any('/*whatever' => {whatever => ''} => sub {
    my $c = shift;
    my $message = 'PAGE 404 '.$c->tx->{original_remote_address}." ".$c
+->tx->req->url;
    $self->app->log->debug($message); # . Dumper($c->tx)
    $c->render(status => 404, text => $message);
  });
}

[download]

In reply to Re: request logging with Mojolicious by alexander_lunev
in thread request logging with Mojolicious by tomgracey

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.