Journal begins at Wed 17:34:06 UTC, ends at Wed 17:53:34 UTC. Inspect service logs and apply how to fix SmokePing SSH probe on Debian Buster patch if you see the following error. ├─5289 /usr/bin/perl /usr/sbin/smokeping -pid-dir=/run/smokeping Process: 5273 ExecStart=/usr/sbin/smokeping -pid-dir=/run/smokeping (code=exited, status=0/SUCCESS) Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Wed 18:29:16 UTC 5s agoįile:/usr/share/doc/smokeping/examples/systemd/slave_nf rvice - Latency Logging and Graphing System.Urlformat = expect = Logged in as secret-userĪlerts = offlineatstartup,hostdown_with_stateĪlerts = offlineatstartup,hostdown_with_state,rttdetect,rtt_avg_increased
Title = DNS check using local DNSĪlerts = hostdown_with_state,rttdetect,rtt_avg_increasedĮxtraargs = -user secret-user:secret-password Title = DNS check using second Google Public DNS server Title = DNS check using first Google Public DNS server Title = DNS check using Google Public DNS $ cat << EOF | sudo tee /etc/smokeping/config.d/TargetsĪlerts = offlineatstartup,hostdown_with_state,rttdetect,rtt_avg_increased,lossdetect Precisely define targets using defined probes and alerts. Pattern = Avgratio(historic => 20, current => 2, comparator=>'>', percentage => 150)Ĭomment = average latency from last 2 samples increased over 150% when compared to average from last 20 samples I will use default settings, which means 20 pings every 5 minutes. $ sudo apt install -no-install-recommends smokeping dnsutils curlĪt first, check out the database settings as you cannot easily modify these later on. Install smokeping package, but skip recommended packages. SmokePing instance configured using the following configuration Install and configure SmokePing Keep track of network latency using SmokePing on Debian Bullseye.
0 kommentar(er)
