Document that `sdb-alert` depends on `sysstat`

Feedback Doc Feedback
1

Some checks that sdb-alert does seem to depend on iostat and sar:

memoryCommitted ........................ [UNAVAILABLE]
UNAVAILABLE memoryCommitted unavailable on host 127.0.0.1: exec: "sar": executable file not found in $PATH

diskLatencyWrite ....................... [UNAVAILABLE]
UNAVAILABLE diskLatency unavailable on host 127.0.0.1: exec: "iostat": executable file not found in $PATH

swapUsage .............................. [UNAVAILABLE]
UNAVAILABLE swapUsage unavailable on host 127.0.0.1: exec: "sar": executable file not found in $PATH

diskLatencyRead ........................ [UNAVAILABLE]
UNAVAILABLE diskLatency unavailable on host 127.0.0.1: exec: "iostat": executable file not found in $PATH

cpuIdle ................................ [UNAVAILABLE]
UNAVAILABLE cpuUtilization unavailable on host 127.0.0.1: exec: "sar": executable file not found in $PATH

majorPageFaults ........................ [UNAVAILABLE]
UNAVAILABLE majorPageFaults unavailable on host 127.0.0.1: exec: "sar": executable file not found in $PATH

The output above is the result of /usr/bin/sdb-report send-alert --config-file /etc/singlestore-monitoring.yml with the following config for /etc/singlestore-monitoring.yml:

location:
  email:
    receivers:
      - engineering@cyberfusion.nl
    sender: engineering@cyberfusion.nl
    server:
      host: smtp.prorelay.nl
      port: 587
      username:
      password:

I think it would be worth adding to the docs that sysstat is a dependency.

2

We’ve added a documentation ticket to get this page updated. Thanks for pointing it out!

1 Like