From 6c8598c75267c3609ad0a4505851ef7ddb444c0c Mon Sep 17 00:00:00 2001 From: Johannes Findeisen Date: Sun, 12 Feb 2023 09:46:09 +0100 Subject: [PATCH] Just more ideas... --- bin/linspector | 2 +- etc/linspector.conf | 10 +++++++--- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/bin/linspector b/bin/linspector index c421e56..f0e5786 100755 --- a/bin/linspector +++ b/bin/linspector @@ -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 # stable version. -__version__ = '0.19.62.dev1' +__version__ = '0.19.63.dev1' __author__ = 'Johannes Findeisen ' diff --git a/etc/linspector.conf b/etc/linspector.conf index 7323983..78697b6 100644 --- a/etc/linspector.conf +++ b/etc/linspector.conf @@ -2,7 +2,8 @@ [linspector] ; report core errors to the following users 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_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 @@ -15,7 +16,7 @@ log_file_size = 1 log_file_size_bytes = 100000 pid_file = /var/run/user/1000/linspector.pid ; 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 ; 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. @@ -97,8 +98,11 @@ sms_resend_count = 5 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 -; httpserver example. +; httpd example. [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. ; every type can be configured in it's own ini file in etc/types; there no type name as prefix is not needed.