no access logs by default?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

no access logs by default?

Ryan Zezeski
Is this intentional?  It seems like odd default behavior.  If it is intentional then perhaps a blurb on the wiki would be nice (I'll do it if someone asks nicely :) ).  I had to dig through the code.  I'm using the master branch, for what it's worth.

For those that want to know, to turn on access logs, add the following to app.config.

{webmachine, [{webmachine_logger_module, webmachine_logger}]}

If you want all access logs in their own dir then add the following to the riak_core list in app.config.

{http_logdir, "log/access"}

-Ryan

_______________________________________________
riak-users mailing list
[hidden email]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Reply | Threaded
Open this post in threaded view
|

Re: no access logs by default?

Justin Sheehy
Hi, Ryan.

On Tue, Mar 1, 2011 at 8:07 PM, Ryan Zezeski <[hidden email]> wrote:

> Is this intentional?  It seems like odd default behavior.

Most databases, including Riak, do not write to a file every time you
do a GET, SELECT, or other query as appropriate.

This is because the additional disk I/O of an access log imposes a
performance cost that many do not wish to pay.  As you note, it can be
turned on -- but we believe that by default production users generally
are happier with it off and do not expect such a human-readable log
for database accesses.

I agree that the way to turn it on should be clearly documented.  I
would add that we should make sure that the documentation warns people
not to turn it on except in testing/debugging scenarios.

Best,

-Justin

_______________________________________________
riak-users mailing list
[hidden email]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Reply | Threaded
Open this post in threaded view
|

Re: no access logs by default?

Mark Phillips-4
Quick update here - This info is now on the wiki.

http://wiki.basho.com/Configuration-Files.html#webmachine_logger_module

(h/t to Ryan for adding it).

Mark

On Tue, Mar 1, 2011 at 6:02 PM, Justin Sheehy <[hidden email]> wrote:

> Hi, Ryan.
>
> On Tue, Mar 1, 2011 at 8:07 PM, Ryan Zezeski <[hidden email]> wrote:
>
>> Is this intentional?  It seems like odd default behavior.
>
> Most databases, including Riak, do not write to a file every time you
> do a GET, SELECT, or other query as appropriate.
>
> This is because the additional disk I/O of an access log imposes a
> performance cost that many do not wish to pay.  As you note, it can be
> turned on -- but we believe that by default production users generally
> are happier with it off and do not expect such a human-readable log
> for database accesses.
>
> I agree that the way to turn it on should be clearly documented.  I
> would add that we should make sure that the documentation warns people
> not to turn it on except in testing/debugging scenarios.
>
> Best,
>
> -Justin
>
> _______________________________________________
> riak-users mailing list
> [hidden email]
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>

_______________________________________________
riak-users mailing list
[hidden email]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com