Troubleshooting and Execution
Disabling Automated Updates
By default, LogScale tries to provide the latest the LogScale collector installers, if you have connection issues or the server is not connected to the internet, you may need to disable automatic updates.
Set the server setting to
disabledIn this case, updates are disabled. This is useful in airgapped environments.
Not set. In this case, LogScale uses our update server via a URL defined in the code.
We strongly encourage all users to use
https:// and the
LogScale Collector enforces using
https:// for URLs, however
it is possible to send to
http:// addresses by supplying the
command line flag.
This is only for testing purposes and not supported in production.
By default, the configuration file points to the directory
var/lib/humio-log-collector as the storage for
Stop the LogScale Collector service --humio-log-collector.service.
database.dbfile to reset the state of the installation.
Restart the LogScale LogScale Collector service.
You can troubleshoot the Falcon LogScale Collector using Using Console Stderr or the Debug Log.
Using Console Stderr
The LogScale Collector sends information to stderr if run from the CLI, the information is sent using JSON format and the detail level is controlled by the log-level. The log-level can be specified using two different approaches (highest priority first):
Using a command line argument: --log-level debug
Configuring a log-level in the config file (yaml):
The following log-levels are supported:
trace (highest verbosity)
The --log-pretty command line argument enables pretty-printing of console output for all logs, it has no effect on logs sent to LogScale, they use JSON format.
The Falcon LogScale Collector debug log can be sent to a LogScale
instance by setting the
HUMIO_DEBUG_LOG_TOKEN environment variables:
The default log-level for info sent to the LogScale instance is trace, it is possible to change this with an environment variable:
To stop sending the debug log the environment variables need to be undefined.