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

Some more logging stuff. log is now a global function as argument.

Browse source 
Don't know if it is good, but it made things easier to me.
This commit is contained in:
Johannes Findeisen 2022-10-06 02:42:15 +02:00
commit 7e228a3196
33 changed files with 188 additions and 204 deletions
Download patch file Download diff file Expand all files Collapse all files

19
etc/linspector.conf
View file

@ -2,24 +2,24 @@
[linspector]
; report core errors to the following users
error_receivers = admin@example.com
; available log levels are: "error", "warning", "info" and "debug".
; available log levels are: "error", "warning", "info" and "debug". if no log_level is set, it will be critical only.
log_level= debug
log_file = ~/code/linspector/linspector/log/linspector.log
; number of log files to be kept. i recommend to use the lowest sensible value for keeping performance hight. so set
; number of log files to be kept. i recommend to use the lowest sensible value for keeping performance high. so set
; the size of the log file higher to increase the log history.
log_file_count = 50
log_file_count = 25
; log file size in megabytes as float.
log_file_size = 1
;log_file_size = 1
; log file size in bytes as int. you can set to bytes if you want to set a value lower then 1 megabyte. but it will
; only be used when log_file_size is not set.
log_file_size_bytes = 10485760
;log_file_size_bytes = 10485760
pid_file = /var/run/user/1000/linspector.pid
; plugins separated by ','. no whitespaces allowed. not case sensitive.
; 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 separated by ','. no whitespaces allowed! not case sensitive.
tasks = SQLite
notifications = SMS
; maybe the run_mode is obsolete because this will be a daemon but maybe it is useful for one time execution?
@ -37,8 +37,9 @@ start_scheduler = true
scheduler_mode = process
max_threads = 2048
; i recommend to set this to your number of CPU cores available when running on a dedicated Linspector host. but if the
; system is running other services you should lower this value when you have too high CPU load.
max_processes = 24
; system is running other services you should lower this value when you have too high CPU load. if you have enough
; resources this value really can be higher then your available CPU cores.
max_processes = 48
; if timezone is not set, UTC is used by default.
timezone = CET
; this is for scheduling jobs to not run all at the same time. this should be set to the lowest interval you use. it

1
etc/monitors/network1/gateway.conf
View file

@ -5,6 +5,7 @@
description = Cable Provider
service = net.fritzboxuplink
hosts = 192.168.0.1,192.168.23.24,@group1,@testgroup1
; this only depends on the SLA you made with the product owner.
interval = 60
; optional options when using notifications, plugins, services or tasks. btw. they still can be a required argument by