refactor(userspace/falco): make sinsp logging part of the configurati…

…on (default to false)

Signed-off-by: Jason Dellaluce <jasondellaluce@gmail.com>

falco.yaml

@@ -98,6 +98,11 @@ log_syslog: true
 # "alert", "critical", "error", "warning", "notice", "info", "debug".
 log_level: info
 
+# Whether or not logging from libsinsp is enabled. If true, logs
+# coming from libsinsp are managed by Falco and comply to the configured
+# values of log_level, log_stderr, and log_syslog. Defaults to false.
+log_sinsp: false
+
 # Minimum rule priority level to load and run. All rules having a
 # priority more severe than this level will be loaded/run.  Can be one
 # of "emergency", "alert", "critical", "error", "warning", "notice",

userspace/falco/configuration.cpp

@@ -183,6 +183,8 @@ void falco_configuration::init(string conf_filename, const vector<string> &cmdli
 
 	falco_logger::set_level(m_log_level);
 
+	falco_logger::set_sinsp_logging(m_config->get_scalar<bool>("log_sinsp", false));
+
 	m_output_timeout = m_config->get_scalar<uint32_t>("output_timeout", 2000);
 
 	m_notifications_rate = m_config->get_scalar<uint32_t>("outputs.rate", 1);