[Archivesspace_Users_Group] Logging

Mark Cooper mark.cooper at lyrasis.org
Thu Aug 4 12:52:39 EDT 2016

Hi Michael,

That log level setting is for the backend application only, which tends to be the noisiest by far.

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).

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.



Mark Cooper
Technical Lead, Hosting and Support
email: mark.cooper at lyrasis.org
skype: mark_c_cooper
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Michael Bond <Michael.Bond at mail.wvu.edu>
Sent: Wednesday, August 3, 2016 4:44:19 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Logging

we are having an issue with  the archive space logs growing quickly in size, 3 to 10gb per day.

I've got log rotate running every 5 minutes trying to keep up with it.

I have the log level set to fatal in the config:
AppConfig[:backend_log_level] = "fatal"

But it is still logging  information marked as "INFO" into the log.  For example:
2016-08-03 07:40:45.811:INFO:/:  Rendered site/_advanced_search.html.erb (3.0ms)|

Every search seems to log about 60+ lines to the log file ... Is there a way to actually limit what is logged?

ArchivesSpace has been restarted, many times, since changing the backend_log_level.


Michael Bond
WVU Libraries
Office: 304-293-0340
Mobile: 304-282-0640
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160804/880a6cfd/attachment.html>

More information about the Archivesspace_Users_Group mailing list