Skip to content
Snippets Groups Projects
  1. Jun 13, 2017
    • Sergey Joseph Ivanov's avatar
      Fix file handle comparison · ff80f918
      Sergey Joseph Ivanov authored
      '==' can not compare file handles. We can use fileno() function to
      compare numerically file numbers. Code without this returns
      "connection successful" when it timeouts and $fd is "undefined".
      ff80f918
  2. Nov 18, 2015
  3. Nov 16, 2015
  4. Oct 23, 2015
  5. Oct 22, 2015
  6. Apr 07, 2015
  7. Apr 02, 2015
  8. Jan 23, 2015
  9. Dec 09, 2014
  10. Jan 07, 2014
  11. Dec 31, 2013
  12. Dec 17, 2013
    • Mark Harrison's avatar
      Fix error when reading meminfo · 97ff6b23
      Mark Harrison authored
      On some systems, there are lines in /proc/meminfo that don't match the regex.
      Currently these cause resmon to throw an error and give a blank metric. This
      change skips those metrics rather than throwing an error.
      97ff6b23
  13. Dec 13, 2013
  14. Dec 12, 2013
  15. Nov 08, 2013
  16. Jul 18, 2013
  17. Jul 09, 2013
  18. Jul 03, 2013
  19. Jun 20, 2013
  20. Jun 19, 2013
  21. Jun 09, 2013
  22. Jun 17, 2013
  23. Jun 07, 2013
  24. Apr 30, 2013
  25. Apr 16, 2013
  26. Mar 01, 2013
    • Mark Harrison's avatar
      Fix per-check interval/cached metrics · 08e7243a
      Mark Harrison authored
      Credit: Michal Racek <michal.racek@t-systems.sk>
      
      In Resmon 1, it was possible to add an interval parameter to an individual
      check to give it a larger check interval than regular checks (cached results
      would be returned in the meantime). This functionality wasn't properly carried
      over into resmon 2, and this commit fixes that.
      08e7243a
  27. Feb 28, 2013
  28. Dec 26, 2012
  29. Dec 13, 2012
  30. Dec 12, 2012
    • Mark Harrison's avatar
      Don't store blank data if we fail to get anything from the shared state file · 4160ac71
      Mark Harrison authored
      Occasionally on some systems, the data returned from the shared state file is
      bad/blank, despite locking. Ideally we'd find the cause of this and fix it,
      but various attempts haven't identified exactly why this happens (including
      running fsync after writing and before unlocking). If the data returned is
      blank, we should use the latest available data rather than returning blank
      data to the user/monitoring system.
      4160ac71
Loading