1. 17 Dec, 2018 4 commits
  2. 14 Dec, 2018 1 commit
  3. 13 Dec, 2018 2 commits
  4. 10 Dec, 2018 1 commit
  5. 07 Dec, 2018 1 commit
  6. 05 Dec, 2018 1 commit
  7. 19 Nov, 2018 1 commit
  8. 15 Nov, 2018 2 commits
  9. 11 Nov, 2018 2 commits
  10. 07 Nov, 2018 1 commit
  11. 04 Nov, 2018 1 commit
  12. 01 Nov, 2018 1 commit
  13. 31 Oct, 2018 2 commits
  14. 30 Oct, 2018 1 commit
  15. 26 Oct, 2018 2 commits
  16. 24 Oct, 2018 1 commit
  17. 22 Oct, 2018 3 commits
  18. 18 Oct, 2018 1 commit
  19. 17 Oct, 2018 1 commit
  20. 15 Oct, 2018 2 commits
  21. 12 Oct, 2018 2 commits
  22. 11 Oct, 2018 1 commit
  23. 08 Oct, 2018 1 commit
  24. 06 Oct, 2018 1 commit
  25. 05 Oct, 2018 1 commit
  26. 03 Oct, 2018 1 commit
  27. 25 Sep, 2018 1 commit
  28. 21 Sep, 2018 1 commit
    • Björn Rabenstein's avatar
      Replace lovoo/ipmi_exporter by soundcloud/ipmi_exporter (#1029) · 50084b8f
      Björn Rabenstein authored
      Frankly, I would prefer to list both as they have quite different
      approaches. Lovoo's exporter runs on the IPMI-supervised host and uses
      the `dev/ipmi0` device to server metrics. This is straight-forward but
      doesn't work if the host is powered down. However, in some secnarios,
      it's the whole point of IPMI to be able to work with machines while
      they are powered down or stuck in the boot process. If you need
      metrics in those scenarios, too, the SoundCloud exporter works
      better. It uses the blackbox exporter approach and is thus (arguably)
      a tad more complicated to set up.
      
      If I _had_ to choose one and only one IPMI exporter, I would pick the
      SoundCloud one as it covers all scenarios.  Since @brian-brazil
      insisted so far to only ever list one solution for a certain thing to
      export, this commit _replaces_ the Lovoo exporter by the SoundCloud
      exporter.
      
      Discuss!
      Signed-off-by: 's avatarbeorn7 <beorn@soundcloud.com>
      50084b8f