armin/linspector
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Refactoring, fixes and really a lot of new ideas...

Browse source
This commit is contained in:
Johannes Findeisen 2022-09-28 08:27:51 +02:00
commit e4ffdedb56
46 changed files with 191 additions and 763 deletions
Download patch file Download diff file Expand all files Collapse all files

23
etc/linspector.conf
View file

@ -14,10 +14,18 @@ plugins = Lish,HTTPServer
; monitor and the monitor can add tasks to the global settings... need to think about it.
; tasks separated by ','. no whitespaces allowed
tasks = SQLite
notification = SMS
notifications = 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
; members to send notifications to if something internally in Linspector went wrong.
members = superadmin@example.com,developers@example.com
; hostgroup parents; if the hostgroup "group1" is down, don't alert for the hosts in group2. see TODO for more
; information.
[hostgroupparents]
; hostgroup group1 is parent of group2
group1 = group2
; 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.
@ -29,13 +37,20 @@ group1 = host1,host2,host3
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
; using groups inside groups. but need to take care about recursive dependencies.
group4 = host10,host11,host12,@group3
; member groups to define recipients for notifications. see hostgroups for more details.
[membergroups]
admins = admin1@example.com,admin2@example.com,admin3@example.com
developers = hanez@example.com
; 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
network1_members = admin@example.com,@admins
; 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.
@ -58,9 +73,11 @@ email_resend = 10
speedtest_interval = 3600
speedtest_url = https://go.microsoft.com/fwlink/?Linkid=850641
; tasks executed at the end of each monitor execution. this is for storing data for longtime analysis. not every task
; is storing results and this feature is fully optional. Linspector must run even without activated tasks!
[tasks]
mariadb_database = linspector
mariadb_host = 10.0.0.254
mariadb_password = PASSWORD
mariadb_port": 3306
mariadb_port = 3306
mariadb_user = USER