Search: logging

…Below you can find detailed description of all SPE configuration settings, together with some usage tips. Table of Contents Toggle Generic settings server.bind_ip, server.port server.identifier server.umask Paths, locations server.user.home bsapi.path server.shared.path technologies.configuration server.license Logging server.logging.level server.logging.destination server.logging.file server.logging.file.rotation server.logging.file.purge_count server.logging.enable_async server.logging.database.identifier Initialization server.require_all_configured_technologies server.technology_multithread_initialization server.technology_multithread_initialization.n_threads Database server.db.save_results server.db.engine server.db.sqlite.data_source server.db.mariadb.host, server.db.mariadb.port server.db.mariadb.db, server.db.mariadb.user, server.db.mariadb.password server.db.mariadb.options, server.db.mariadb.max_connections Audio Source Profile server.audio_source_profiles_cache_size…

…server.port = 8600 # Server logging # Level (trace, debug, information, warning, error, fatal) server.logging.level = information # Destination (console, file, database) # Logging to database is supported only for MySQL server.logging.destination = file # Path to file where log is stored server.logging.file = ${application.dir}log/phxspe.log Did you notice the server.logging.file directive? They present the first example of using variables in…

…technology model, results JSON data rest_result_tae TAE processing results – file, used technology model, results JSON data rest_result_vad VAD processing results – file, used technology model, results JSON data SPE logging to database Storing SPE logs to database is available only for MariaDB / MySQL. This is mainly for performance reasons – SQLite is not designed for high concurrency, i.e….