From b4188578302c6e71b5b62881c86fdc6e849531b5 Mon Sep 17 00:00:00 2001 From: Sam Saffron Date: Fri, 22 Mar 2019 14:11:21 +1100 Subject: [PATCH] DEV: document max_logster_logs in discourse_defaults.conf This cleans up logster configuration a bit cause we no longer have to check if we respond_to anything and keeps the logster limit properly documented Followup on da578e92 --- config/discourse_defaults.conf | 3 +++ config/initializers/100-logster.rb | 4 +--- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/config/discourse_defaults.conf b/config/discourse_defaults.conf index 421f72401c1..784d395d369 100644 --- a/config/discourse_defaults.conf +++ b/config/discourse_defaults.conf @@ -205,3 +205,6 @@ force_anonymous_min_per_10_seconds = 3 # flood the queue max_old_rebakes_per_15_minutes = 300 +# maximum number of log messages in /logs +max_logster_logs = 1000 + diff --git a/config/initializers/100-logster.rb b/config/initializers/100-logster.rb index eeed5005d40..50af0b12db9 100644 --- a/config/initializers/100-logster.rb +++ b/config/initializers/100-logster.rb @@ -72,9 +72,7 @@ if Rails.env.production? Logster.config.env_expandable_keys.push(:hostname, :problem_db) end -if GlobalSetting.respond_to?(:max_logster_logs) - Logster.store.max_backlog = GlobalSetting.max_logster_logs -end +Logster.store.max_backlog = GlobalSetting.max_logster_logs # middleware that logs errors sits before multisite # we need to establish a connection so redis connection is good