1. 27 Jan, 2021 2 commits
    • Łukasz Nowak's avatar
      Release 0.115 · bd63a31a
      Łukasz Nowak authored
      bd63a31a
    • Łukasz Nowak's avatar
      check_surykatka_json: Minimise message variation · 587c0792
      Łukasz Nowak authored
      Monitoring is about states, not exact values, so report the states, as
      otherwise it results with bloating databases, very long accesses to results
      and long synchronisations.
      
      Instead of many entries like:
      
      http://url/ : http_query: OK status code 302 on IPs IP elapsed_time: ERROR IP IP replied in 5.02s which is longer than maximum 5.00s
      http://url/ : http_query: OK status code 302 on IPs IP elapsed_time: ERROR IP IP replied in 5.03s which is longer than maximum 5.00s
      http://url/ : http_query: OK status code 302 on IPs IP elapsed_time: ERROR IP IP replied in 5.04s which is longer than maximum 5.00s
      http://url/ : http_query: OK status code 302 on IPs IP elapsed_time: ERROR IP IP replied in 5.01s which is longer than maximum 5.00s
      http://url/ : http_query: OK status code 302 on IPs IP elapsed_time: OK IP IP replied in 0.08s which is shorter than maximum 5.00s
      http://url/ : http_query: OK status code 302 on IPs IP elapsed_time: OK IP IP replied in 1.37s which is shorter than maximum 5.00s
      http://url/ : http_query: OK status code 302 on IPs IP elapsed_time: OK IP IP replied in 0.09s which is shorter than maximum 5.00s
      http://url/ : http_query: OK status code 302 on IPs IP elapsed_time: OK IP IP replied in 1.37s which is shorter than maximum 5.00s
      http://url/ : http_query: OK status code 302 on IPs IP elapsed_time: OK IP IP replied in 0.09s which is shorter than maximum 5.00s
      
      It's minimised to:
      
      http://url/ : http_query: OK status code 302 on IPs IP elapsed_time: ERROR IP IP replied in more time than maximum 5.00s
      http://url/ : http_query: OK status code 302 on IPs IP elapsed_time: OK IP IP replied in less time than maximum 5.00s
      
      This affects:
      
       * bot_status
       * http_query
      
      Obviously some information are removed from the monitor, but anyway they are
      just text entries and not parsable. So other approaches shall be used to make
      graphs from those values, which is not covered by pure promise status.
      587c0792
  2. 22 Jan, 2021 1 commit
  3. 20 Jan, 2021 1 commit
    • Jérome Perrin's avatar
      apachedex: expect apachedex options to be passed as a file · cc153a6e
      Jérome Perrin authored
      Arguments passed to apachedex are complex, they contain quotes, backslashes,
      spaces and they are propagated through several levels of buildout profiles
      and scripts.
      Simplify all this by relying on argparse ability of passing arguments from
      a file. Users of this tool are now expected to generate a config file and
      specify the path of this config file as an arguments.
      cc153a6e
  4. 11 Jan, 2021 1 commit
  5. 11 Nov, 2020 2 commits
  6. 10 Nov, 2020 2 commits
  7. 20 Oct, 2020 1 commit
  8. 13 Oct, 2020 1 commit
  9. 18 Sep, 2020 1 commit
    • Jérome Perrin's avatar
      Fix random test failures · 2699c3bd
      Jérome Perrin authored
      "test_networkbench: increase resolution time tolerance" addresses [this](https://erp5.nexedi.net/test_result_module/20200911-8C18D791/14):
      
      ```
      ======================================================================
      FAIL: test_dnsbench_fail (slapos.test.test_networkbench.TestDNSBench)
      Test dns failure resolution
      ----------------------------------------------------------------------
      Traceback (most recent call last):
      File "/srv/slapgrid/slappart20/srv/testnode/cum/inst/test0-0/parts/slapos.toolbox/slapos/test/test_networkbench.py", line 66, in test_dnsbench_fail
      self.assertLess(info[3], 1)
      AssertionError: 2.0736539363861084 not less than 1
      ```
      
      "cpu load plugin: fix test and minor cleanups" addresses [this](https://erp5.nexedi.net/test_result_module/20200911-C444DB47/13):
      
      ```
      ======================================================================
      ERROR: test_check_cpu_load_run (slapos.test.promise.plugin.test_check_server_cpu_load.TestCheckServerCPULoad)
      ----------------------------------------------------------------------
      Traceback (most recent call last):
        File "/srv/slapgrid/slappart9/srv/testnode/bvi/inst/test0-0/parts/slapos.toolbox/slapos/test/promise/plugin/test_check_server_cpu_load.py", line 48, in test_check_cpu_load_run
          self.launcher.run()
        File "/srv/slapgrid/slappart9/srv/testnode/bvi/soft/65dbbd3d11daa99cf78c9566a0a4798e/parts/slapos.core-repository/slapos/grid/promise/__init__.py", line 884, in run
          failed_promise_output))
      PromiseError: Promise 'server-cpu-load-promise.py' failed with output: Error: Promise timed out after 0.5 seconds
      ```
      Some more fixes are in slapos!809
      
      See merge request !85
      2699c3bd
  10. 15 Sep, 2020 1 commit
  11. 14 Sep, 2020 4 commits
  12. 11 Sep, 2020 2 commits
  13. 10 Sep, 2020 1 commit
  14. 09 Sep, 2020 1 commit
  15. 25 Aug, 2020 2 commits
  16. 24 Aug, 2020 1 commit
  17. 21 Aug, 2020 3 commits
  18. 03 Jun, 2020 4 commits
  19. 15 May, 2020 5 commits
  20. 04 May, 2020 3 commits
  21. 30 Apr, 2020 1 commit