[checkmk-commits] Better wording of AV option log_rowlimit

Module: check_mk Branch: master Commit: 67cb3181b0f47916865cc964ca6a7c723095aa07 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=67cb3181b0f479… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Fri Mar 10 12:11:11 2017 +0100 Better wording of AV option log_rowlimit Change-Id: I918bb1c4642d977a25670e97d6b9b27a64324530 --- web/htdocs/availability.py | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/web/htdocs/availability.py b/web/htdocs/availability.py index 7af709d..c018866 100644 --- a/web/htdocs/availability.py +++ b/web/htdocs/availability.py @@ -494,11 +494,17 @@ def get_avoption_entries(what): "single", True, Integer( - title = _("Log row limit"), - help = _("Limit the fetched rows of logfile in order to avoid " - "a hanging system. A value of zero means no limit."), + title = _("Limit processed data"), + help = _("The availability is computed by processing entries from a data table " + "of historic events and state phases. In order to avoid a hanging system " + "in cases where your time range and filtering would accept a vast amount " + "of data entries, the number of processed entries is limited. You can raise " + "this limit here if you really need to process a huge amount of data. Set this " + "to zero in order to disable the limit."), + label = _("process at most"), + unit = _("status entries"), + minvalue = 1, default_value = 5000, - minvalue = 0, )), ]