-
Notifications
You must be signed in to change notification settings - Fork 12
07 Troubleshooting
Sean Vreeland edited this page Mar 19, 2019
·
4 revisions
Last updated: 18 MAR 2019 by @seanvree
NOTE: This page is currently updated for the Logarr 5.0 release ~ 01 APR 19.
1) Why does Logarr take a long time to load?
- By design, Logarr does not use a database or any applications to store your log files. Therefore, EVERY TIME you load the Logarr UI, it must "download" all of your log files into the browser.
- It is imperative that you ensure your applications are rolling their logs properly. If that functionality is not built into the app you are using, you should contact that developer. Srsly tho - any application that is well developed should have this functionality.
- From our experience, Logarr starts to lag if an individual log is larger than 2MB, and starts to become unusable at 3MB. Of course, this is heavily dependant on your environment, PHP settings, browser speed, etc.
- We are exploring the option to add a database. However, we want to keep this application light and compatible with all environments, therefore, it's not on the top of the to-do list.