You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
as in the subject, it would be useful to have a glance at uptime&disk info next to lsb info, it could be activated upon configuration (i.e. apt-dater.conf)
Or you could make the whole parenthesis "(Debian 7.5 wheezy; 3.14-1-amd64)" (in my case) programmable, it could be an editable script giving just one line of output.
Thanks
The text was updated successfully, but these errors were encountered:
making the parenthesis content configurable sounds like a good idea.
apt-dater is not designed to present live values of uptime/disk info/load (this would require periodic [expensive] updates via SSH all the time apt-dater is running). Especially observing disk usage or load sounds like a monitoring task...
I know that apt-dater is not a live monitoring system, in my mind the status (or the script) would be read (run) only upon refresh ("G"), it could be a hook of some sort...
I mean, hooks are already supported, you just need to, say, get the first output line of one of them (it could be called "status.sh")
EDIT: I've re-read the doc and I realized that hooks are run on the "client-side" (not on the monitored host, is it correct? In this case of course it's not possible to use them (hooks) to get the status of the monitored machine, thus you could think about introducing hooks on the target machine
as for the hooks running on the client (monitoring side) is it possible to get the execution result? (not the return code, but some output from the command)
Hi,
as in the subject, it would be useful to have a glance at uptime&disk info next to lsb info, it could be activated upon configuration (i.e. apt-dater.conf)
Or you could make the whole parenthesis "(Debian 7.5 wheezy; 3.14-1-amd64)" (in my case) programmable, it could be an editable script giving just one line of output.
Thanks
The text was updated successfully, but these errors were encountered: