Just more ideas...
This commit is contained in:
parent
484ad6e3b3
commit
6c8598c752
2 changed files with 8 additions and 4 deletions
|
|
@ -18,7 +18,7 @@ from linspector.core.monitors import Monitors
|
||||||
|
|
||||||
# i currently only increase the 3rd number because the goal is that 0.19.* will become the first
|
# i currently only increase the 3rd number because the goal is that 0.19.* will become the first
|
||||||
# stable version.
|
# stable version.
|
||||||
__version__ = '0.19.62.dev1'
|
__version__ = '0.19.63.dev1'
|
||||||
__author__ = 'Johannes Findeisen <you@hanez.org>'
|
__author__ = 'Johannes Findeisen <you@hanez.org>'
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,8 @@
|
||||||
[linspector]
|
[linspector]
|
||||||
; report core errors to the following users
|
; report core errors to the following users
|
||||||
error_receivers = admin@example.com
|
error_receivers = admin@example.com
|
||||||
; available log levels are: "error", "warning", "info" and "debug". if no log_level is set, it will be critical only.
|
; available log levels are: "critical", "error", "warning", "info" and "debug". if no log_level is set, it will be set
|
||||||
|
; to "critical".
|
||||||
log_level = debug
|
log_level = debug
|
||||||
;log_file = ~/code/linspector/linspector/log/linspector.log
|
;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 high. so set
|
; number of log files to be kept. i recommend to use the lowest sensible value for keeping performance high. so set
|
||||||
|
|
@ -15,7 +16,7 @@ log_file_size = 1
|
||||||
log_file_size_bytes = 100000
|
log_file_size_bytes = 100000
|
||||||
pid_file = /var/run/user/1000/linspector.pid
|
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 = rpc,httpserver
|
plugins = api,httpd,lish
|
||||||
; globally configured tasks will always run on all monitors when no task is configured there. if tasks are configured in
|
; 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
|
; 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.
|
; monitor and the monitor can add tasks to the global settings... need to think about it.
|
||||||
|
|
@ -97,8 +98,11 @@ sms_resend_count = 5
|
||||||
email_resend = 10
|
email_resend = 10
|
||||||
|
|
||||||
; every plugin can be configured in it's own ini file in etc/plugins; there no plugin name as prefix is needed. see
|
; every plugin can be configured in it's own ini file in etc/plugins; there no plugin name as prefix is needed. see
|
||||||
; httpserver example.
|
; httpd example.
|
||||||
[plugins]
|
[plugins]
|
||||||
|
api_host = 0.0.0.0
|
||||||
|
httpd_host = 192.168.23.42
|
||||||
|
httpd_port = 8089
|
||||||
|
|
||||||
; if types can or must be configured before use; for now no use case seen.
|
; if types can or must be configured before use; for now no use case seen.
|
||||||
; every type can be configured in it's own ini file in etc/types; there no type name as prefix is not needed.
|
; every type can be configured in it's own ini file in etc/types; there no type name as prefix is not needed.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue