v1.0.0

See CHANGELOG.md

v1.0.0-beta

Release v1.0.0-beta

v0.2.0-beta

Release v0.2.0-beta

v0.1.9

Changed

• WATO option for check: print monitored runtime even if OK (closes #70)

Fixed

• Bakery set a wrong binary path on Windows (robotmk plugin was placed in agentdata root dir); created
  custom file packages for linux and windows. Renamed the custom file packages to robotmk-windows and
  robotmk-linux (solves #73)
• Bakery: fixed wrong key value for utf-8 (closes #72)
• Plugin: Robot Logfile rotation "never" crashes (TypeError) (closes #77)
• Badges and Unicode symbols for S/T/K do not represent worst state (closes #78)
• Time of last execution does not work on discovery level (#74)

v0.1.8

Fixed

• When using a custom service prefix for discovery, the pattern %SPACE% can now
  be used at the prefix end to prevent Multisite cropping the string. (Solves #69)

v0.1.7

Fixed/Changed

• Service prefix "Robot" is eliminated. By default, there is no prefix at all.
  It can be overriden by a custom one. By installing this version, your existing Robot
  services will get new descriptions (=without "Robot"), RRD data tied to the old
  name will be lost. (closes #50)

v0.1.6

Added:

• Inventory blacklist: when using discovery level, now it is possible to blacklist certain nodes which should not be inventorized as services (solves #54)

v0.1.5

Added

• Log/Report/XML files of RF tests are now saved with a timestamp to make debugging easier.
  New WATO option for the check plugin to set the number of days log files should be kept. (solves #56)
• Besides UTF-8, there are two more options in WATO to encode the data between agent and server:
  BASE-64 and zlib compression. The latter is implemented with regard to the upcoming integration
  of RF HTML logs into Checkmk. As soon they are containing screenshot data, compression is needed. Solves #65.
• Added WATO option show_submessages to enable/disable the presence of sub-node messages in tests and suites.

Changed

• WATO option "includedate": in the past, it contained the end timestamp of the node
  itself. This could lead to misunderstandings if discovery level > 0 was used, because
  last execution for services generated from tests were different. In fact this was true,
  but the interesting fact is when the suite was executed last, not a subsuite or test.
  For this reason, the date is now the timestamp of the whole suite execution end.

Fixed

• Support UTF-8, solves problem with german umlaut etc. (closes #55)
• RF States of Keywords are now preserved and not propagated upwards. This is neccessary because
  keywords like 'Run Keyword And Return Status' can wrap kw execution; a failed kw will not fail
  the whole test. With this commit, the cmk-side evaluation of the RF restult tree respects the RF
  state of each node, but does not propagate it. (solves #57 and #58)
• Bakery crashes when RobotMK rule does not contain specific suites (closes #45)
• Multisite crashes ("no closing quotation") when nasty chars from keyword names get into perflabels (closes #64)

v0.1.4

Added

• Bakery/Check: Added spooldir mode; Robotmk plugin can be triggered externally, writes to spooldir of mk agent (#49)
• Check now makes use of HTML badges for WARN/CRIT (#52)

Changed

• Plugin: Set tmpdir on Windows to a fixed path (#47)
• Improved Logging (#48)

Fixed

• No graphs when using a discovery level (#53)

v0.1.3

Added

• Check: Introduce CRITICAL state for thresholds (#22)
• Check: Add WATO option: include execution timestamp into first line (#41)

Fixed

• Check: Solved check crash when only perfdata rule active, not threshold (#40)