Module: check_mk
Branch: master
Commit: cb209b3d9a2e36ae5ed9267782a8ba2be9d7df35
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=cb209b3d9a2e36…
Author: Sebastian Herbord <sh(a)mathias-kettner.de>
Date: Mon Oct 5 10:13:50 2015 +0200
added gb regarding excessive agent output
---
.bugs/2362 | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/.bugs/2362 b/.bugs/2362
new file mode 100644
index 0000000..d5da5b0
--- /dev/null
+++ b/.bugs/2362
@@ -0,0 +1,11 @@
+Title: Excessive Agent output can interfere with check_mk
+Component: core
+State: open
+Date: 2015-10-05 09:44:32
+Targetversion: 1.2.7
+Class: nastiness
+
+Currently check_mk will always try to process all agent output. If the agent produces a
lot of output, some checks may cause excessive cpu load and memory usage, effectively
making the monitoring system unusable.
+To the user this will appear like a bug since the amount of data between agent and
monitoring system is not visualised and not warned about so there is no way for the user
to find the cause of the slowness.
+To remedy this we could add readings and warn/crit levels on the agent output size, agent
response time, execution time and memory usage.
+In addition we should add support for memory profiling of individual checks so that
problematic checks are easier to identify.
\ No newline at end of file