 Archit Bansal
|
3a9370e01b
|
Log custom plugin stderr only if the status is not ok.
Otherwise with plugins that run frequently and report ok status, the
logs are filled with unnecessary noise and significantly increases log
size.
|
2020-08-27 10:17:05 -07:00 |
|
  Kubernetes Prow RobotandGitHub
|
f3ab10eddb
|
Merge pull request #442 from abansal4032/custom-plugin-logs-capture
Capture the logs from stderr of custom plugins
|
2020-07-29 14:18:03 -07:00 |
|
|
Archit Bansal
|
6acf5b1edb
|
Capture the logs from stderr of custom plugins.
|
2020-07-29 11:57:05 -07:00 |
|
|
Archit Bansal
|
f80f3e0dfa
|
Generate status generation logs from custom plugin run only on condition change.
|
2020-07-24 09:39:39 -07:00 |
|
 yuzhiquan
|
9c24be2da4
|
cleanup: using time.Since(t) instead of t.Sub(time.Now())
|
2019-12-05 18:57:53 +08:00 |
|
 Lantao Liu
|
be7cc78aa0
|
Properly close channel when monitor exits.
Signed-off-by: Lantao Liu <lantaol@google.com>
|
2019-10-25 14:11:39 -07:00 |
|
 Michael Grosser
|
3be50a088a
|
untangle plugin runner a bit
add some docs and make it clearer what is actually going on
(parallel rule execution on start and then on timer)
|
2019-10-10 15:46:04 -07:00 |
|
 Yang Guo
|
468a23d09a
|
Run custom plugins immediately on startup
|
2019-06-04 09:42:34 -07:00 |
|
 David Ashpole
|
bf730e9c63
|
add log-counter go plugin
|
2018-06-20 15:55:19 -07:00 |
|
 Andy Xie
|
10dbfef1a8
|
add custom problem detector plugin
|
2017-11-22 10:14:09 +08:00 |
|