Lot of new ideas defined in configuration files and tons of refactoring.
This commit is contained in:
parent
947a14bdde
commit
3de67966f4
49 changed files with 307 additions and 76 deletions
|
|
@ -7,20 +7,38 @@ log_level= verbose
|
|||
log_count = 5
|
||||
log_size = 10485760
|
||||
pid_file = /var/run/user/1000/linspector.pid
|
||||
; plugins separated by ','. no whitespaces allowed
|
||||
plugins = lish,httpserver
|
||||
; plugins separated by ','. no whitespaces allowed. not case sensitive.
|
||||
plugins = Lish,HTTPServer
|
||||
; globally configured tasks will always run on all monitors when no task is configured there. if tasks are configured in
|
||||
; a monitor then maybe only run tasks from the dedicated monitor. maybe it is a good idea to run global tasks in every
|
||||
; monitor and the monitor can add tasks to the global settings... need to think about it.
|
||||
; tasks separated by ','. no whitespaces allowed
|
||||
tasks = sqlite
|
||||
tasks = SQLite
|
||||
notification = SMS
|
||||
; maybe the run_mode is obsolete because this will be a daemon but maybe it is useful for one time execution?
|
||||
; in uplink the available run_modes were cron, daemon and foreground
|
||||
run_mode = cron
|
||||
|
||||
; every notification can be configured in it's own ini file in etc/notifications; there no notification name as prefix
|
||||
; is needed. see email example.
|
||||
; a flexible way to define groups of hosts which can be used by monitors as target for monitoring for easily monitor
|
||||
; groups without adding a monitor for each host. for some more information see the "hosts" section in gateway.conf.
|
||||
; hostgroups can be defined in separate files in etc/hostgroups to be more flexible.
|
||||
[hostgroups]
|
||||
; add single hosts
|
||||
group1 = host1,host2,host3
|
||||
; add a range of ip addresses. maybe a different range operator should be chosen but for now i think ">" is sexy... :)
|
||||
group2 = 192.168.1.1>192.168.1.127
|
||||
; add a combination of hosts and ranges
|
||||
group3 = host1,host2,host3,192.168.1.1>192.168.1.127
|
||||
|
||||
; just an idea taken from the old Linspector design. not tried but seems a good idea to add global options to monitor
|
||||
; groups. no idea of an implementation yet.
|
||||
[monitorgroups]
|
||||
; members of monitors to automatically send notifications to all without need to set them in each monitor. members can
|
||||
; be added to monitors in the configuration of each monitor though.
|
||||
network1_members = admin1@example.com,admin2@example.com,admin3@example.com
|
||||
|
||||
; every notification can be configured in it's own configuration file in etc/notifications; there no notification
|
||||
; name as prefix is needed. see email example.
|
||||
[notifications]
|
||||
; values can be overridden in each defined monitor
|
||||
sms_receivers = +number1,+number2
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue