Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #2937] Log View unusable with large logentries table #859
This issue has been migrated from Redmine: https://dev.icinga.com/issues/2937
Created by tgelf on 2012-08-03 12:17:19 +00:00
Log View is so terrible slow that it cannot be used, at least once you have a few million log entries in you database. This is at least true for MySQL. Fixing it is pretty easy, the INNER JOIN makes MySQL believe that it has to copy around a lot of stuff for it's WHERE/ORDER Voodoo. There is an easy workaround for this: just replace the INNER with an OUTER JOIN.
This is done in app/modules/Api/config/views/misc.xml, section TARGET_LOG. Replace 'INNER JOIN l.instance' with 'LEFT JOIN l.instance', and that's it. Query time went down from minutes (!) to a fraction of second here.
2012-08-03 12:22:48 +00:00 by mhein 4c3a848
2012-08-03 12:23:22 +00:00 by mhein 80c9229