<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">Hi Michael,</span><br>
</p>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p><br>
</p>
<p>That log level setting is for the backend application only, which tends to be the noisiest by far.</p>
<p><br>
</p>
<p>For logrotate you can set the max size to something you're happy with (say 1gb, or smaller) and it should rotate the logs at that point (regardless of the time settings).</p>
<p><br>
</p>
<p>You might want to check whether you're getting a lot of bot traffic to the public ui and filter them out at the webserver level.</p>
<p><br>
</p>
<p>Best,</p>
<p>Mark</p>
<p><br>
</p>
<div id="x_Signature">
<div id="x_divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<div name="x_divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<span dir="ltr"><font color="black" face="Calibri,Arial,Helvetica,sans-serif" size="3"><span style="font-size:12pt; background-color:white"><font face="Calibri,Arial,Helvetica,sans-serif"><font color="#282828" face="Calibri,Arial,Helvetica,sans-serif"><font color="#2F2F2F" face="Arial,sans-serif"></font></font></font></span></font></span></div>
<div name="x_divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div>Mark Cooper<br>
</div>
<div>Technical Lead, Hosting and Support</div>
<div>LYRASIS</div>
<div>email: mark.cooper@lyrasis.org</div>
<div>skype: mark_c_cooper<br>
</div>
</div>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Michael Bond
<Michael.Bond@mail.wvu.edu><br>
<b>Sent:</b> Wednesday, August 3, 2016 4:44:19 AM<br>
<b>To:</b> archivesspace_users_group@lyralists.lyrasis.org<br>
<b>Subject:</b> [Archivesspace_Users_Group] Logging</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt">
<div class="PlainText"><br>
we are having an issue with the archive space logs growing quickly in size, 3 to 10gb per day.
<br>
<br>
I've got log rotate running every 5 minutes trying to keep up with it. <br>
<br>
I have the log level set to fatal in the config:<br>
AppConfig[:backend_log_level] = "fatal"<br>
<br>
But it is still logging information marked as "INFO" into the log. For example:<br>
2016-08-03 07:40:45.811:INFO:/: Rendered site/_advanced_search.html.erb (3.0ms)|<br>
<br>
Every search seems to log about 60+ lines to the log file ... Is there a way to actually limit what is logged?
<br>
<br>
ArchivesSpace has been restarted, many times, since changing the backend_log_level.
<br>
<br>
Thanks<br>
<br>
Michael Bond<br>
WVU Libraries<br>
Office: 304-293-0340<br>
Mobile: 304-282-0640<br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
Archivesspace_Users_Group@lyralists.lyrasis.org<br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" id="LPlnk92567">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
</div>
</span></font></div>
</body>
</html>