Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: caa9eae39955383d81b0d3d9fb01cd3ce3d9a760
https://github.com/tribe29/checkmk/commit/caa9eae39955383d81b0d3d9fb01cd3ce…
Author: Sven Panne <sven.panne(a)tribe29.com>
Date: 2019-10-25 (Fri, 25 Oct 2019)
Changed paths:
M gtags.conf
Log Message:
-----------
Build helper/livestatus parts of CMC non-recursively.
This fixes quite a few hacks/TODOs.
Change-Id: Iacd3babd0d9bab32d9e235191b6cda321ff0ffd3
Branch: refs/heads/1.6.0
Home: https://github.com/tribe29/checkmk
Commit: 78cc4cfdf508f5dce2799cd68698c53e66208308
https://github.com/tribe29/checkmk/commit/78cc4cfdf508f5dce2799cd68698c53e6…
Author: Christoph Rauch <christoph.rauch(a)tribe29.com>
Date: 2019-10-25 (Fri, 25 Oct 2019)
Changed paths:
A .werks/10288
Log Message:
-----------
10288 Customer GUI: remove superfluous tt tags
<tt> tags were used but escaped so they were visible. These tags are now removed.
Change-Id: Iaee54453ef9f3f37ea7265db0188a6a6fa65dbb7
Branch: refs/heads/1.5.0
Home: https://github.com/tribe29/checkmk
Commit: dede950c02c122805c667b3882841588e5e91642
https://github.com/tribe29/checkmk/commit/dede950c02c122805c667b3882841588e…
Author: Christoph Rauch <christoph.rauch(a)tribe29.com>
Date: 2019-10-25 (Fri, 25 Oct 2019)
Changed paths:
A .werks/10288
M web/htdocs/wato.py
Log Message:
-----------
10288 FIX Customer GUI: remove superfluous tt tags
<tt> tags were used but escaped so they were visible. These tags are now removed.
Change-Id: Ie29abfed0e358f2c5823c5054cfd2e3f88556cb4
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: fa4cd90474de8a91d333906b53af8c46c432a3e9
https://github.com/tribe29/checkmk/commit/fa4cd90474de8a91d333906b53af8c46c…
Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com>
Date: 2019-10-25 (Fri, 25 Oct 2019)
Changed paths:
A .werks/10195
Log Message:
-----------
10195 Windows Agent: additional parameters for logwatch section
To better control output from the logwatch section the user can set next
parameters for this section:
max_line_length, max_entries, timeout
timeout is measured in seconds and limits the time of the execution of the
every reported log.
max_line_length cuts every line in output data if the size of the line
exceeds the provided value.
max_entries is the maximal count of the entries in every reported event log.
The default values for all above mentioned parameters are -1 and means
unlimited.
Change-Id: Iabcd177f4cf514b3201b7695e0c7846c617b63a5
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 6692d03d33263b56176823b656bedc230691aa8d
https://github.com/tribe29/checkmk/commit/6692d03d33263b56176823b656bedc230…
Author: Tom Baerwinkel <tom.baerwinkel(a)tribe29.com>
Date: 2019-10-25 (Fri, 25 Oct 2019)
Changed paths:
M cmk_base/notify.py
Log Message:
-----------
notify.py: use the logging module
Some code still has to use our handcrafted notify_log function
until alert_handling.py and events.py switched to the logging
module as well.
CMK-1656
Change-Id: I6c0e05ed0bd3d3af157f3193817d0f57903b29e3
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: d5f4fcea0681c03877c9eb85d92ecddfefba264c
https://github.com/tribe29/checkmk/commit/d5f4fcea0681c03877c9eb85d92ecddfe…
Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com>
Date: 2019-10-25 (Fri, 25 Oct 2019)
Changed paths:
A .werks/10194
Log Message:
-----------
10194 Windows Agent: logwatch section size is limited now
Previously the Windows Agent may generate too much data during Windows EventLog
(logwatch) section generation. In fact, size of the data to be send was
unlimited, the Agent could have created a block of data several gigabytes
in the size.
Now default maximal size of the whole logwatch section of the Windows Agent
is limited to 500000 bytes. The value of this limit may be changed in
check_mk.user.yml using variable logwatch.max_size. To have unlimited
section, the value of the max_size should be set in -1
Change-Id: I62d7f036c16a53ef365152523959f45293876d97
Branch: refs/heads/1.6.0
Home: https://github.com/tribe29/checkmk
Commit: 638fbc09c2fe5f088efc06fa287598b6a3684537
https://github.com/tribe29/checkmk/commit/638fbc09c2fe5f088efc06fa287598b6a…
Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com>
Date: 2019-10-25 (Fri, 25 Oct 2019)
Changed paths:
A .werks/10194
Log Message:
-----------
10194 Windows Agent: logwatch section size is limited now
Previously the Windows Agent may generate too much data during Windows EventLog
(logwatch) section generation. In fact, size of the data to be send was
unlimited, the Agent could have created a block of data several gigabytes
in the size.
Now default maximal size of the whole logwatch section of the Windows Agent
is limited to 500000 bytes. The value of this limit may be changed in
check_mk.user.yml using variable logwatch.max_size. To have unlimited
section, the value of the max_size should be set in -1
Change-Id: I62d7f036c16a53ef365152523959f45293876d97
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 64ae200c71d578408e701bbfb8a282b8fc296a0b
https://github.com/tribe29/checkmk/commit/64ae200c71d578408e701bbfb8a282b8f…
Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com>
Date: 2019-10-25 (Fri, 25 Oct 2019)
Changed paths:
M agents/wnx/install/resources/check_mk.yml
M agents/wnx/src/common/cfg_info.h
M agents/wnx/src/common/stop_watch.h
M agents/wnx/src/engine/eventlog/eventlogbase.cpp
M agents/wnx/src/engine/eventlog/eventlogbase.h
M agents/wnx/src/engine/providers/logwatch_event.cpp
M agents/wnx/src/engine/providers/logwatch_event.h
M agents/wnx/watest/test-eventlog.cpp
M agents/wnx/watest/test-section_logwatchevent.cpp
M agents/wnx/watest/test-stop_watch.cpp
Log Message:
-----------
[CMK-3055] - extended logwatch control
- max_size, max_line_legth and timeout
- deep refactored
- fully tested
Change-Id: I5ea2e39cda1710d97756bd060e038e99b913848e