Log Reference
Log Levels
In system monitoring and debugging, logs play a crucial role by recording sequential events or errors that occur within a system. The log levels provide a way to categorize these entries by their severity or importance, which can help in quickly identifying or escalating issues. Common log levels include:
- ERROR: Indicates a significant problem that caused a failure in some part of the system.
- WARN: Signals a potential issue that should be watched or could lead to an error if not addressed.
- INFO: Provides informational messages that highlight the progress of the application.
- DEBUG: Offers detailed diagnostic information used for debugging and understanding system behavior.
Browsermon Log Messages
| Log ID | Level | Message | Description |
|---|---|---|---|
| BM9401 | INFO | [FileConfigStrategy] Starting to load configurations ... | The process of loading configurations has started using the FileConfigStrategy. |
| BM9402 | ERROR | [WatchdogConfigStrategy] Configuration validation failed: {e} | Indicates an error during the configuration validation process. |
| BM9402 | ERROR | [WatchdogConfigStrategy] Could not load configuration successfully | Indicates an error during the configuration loading process in the WatchdogConfigStrategy. |
| BM9401 | INFO | [DefaultConfigStrategy] Starting to load configurations ... | Indicates the configuration loading process has begun using the DefaultConfigStrategy. |
| BM9402 | ERROR | [DefaultConfigStrategy] Configuration validation failed: {e} | Indicates an error during the configuration validation process. |
| BM9402 | ERROR | [DefaultConfigStrategy] Could not load configuration successfully | Indicates an error occurred while loading the configuration in the DefaultConfigStrategy. |
| BM9401 | INFO | [ServerConfigStrategy] Starting to load configurations ... | Indicates the configuration loading process has begun using the ServerConfigStrategy. |
| BM9402 | ERROR | [ServerConfigStrategy] Configuration validation failed: {e} | Indicates an error during the configuration validation process. |
| BM9402 | ERROR | [ServerConfigStrategy] Could not load configuration successfully | Indicates an error occurred while loading the configuration in the ServerConfigStrategy. |
| BM9401 | INFO | [ElasticConfigStrategy] Starting to load configurations ... | Indicates the configuration loading process has begun using the ElasticConfigStrategy. |
| BM9402 | ERROR | [ElasticConfigStrategy] Configuration validation failed: {e} | Indicates an error during the configuration validation process. |
| BM9402 | ERROR | [ElasticConfigStrategy] Could not load configuration: {e} | Indicates an error occurred while loading the configuration in the ElasticConfigStrategy. |
| BM9401 | INFO | [WatchdogConfigStrategy] Received configurations are empty. Skipping update. | Indicates that no valid configuration data was received by the WatchdogConfigStrategy. As a result, the update process is skipped. |
| BM9401 | DEBUG | [WatchdogConfigStrategy] No changes in configurations. Skipping update. | Indicates that there were no changes detected in the configuration (i.e., the old and new configurations are the same). |
| BM9401 | DEBUG | [WatchdogConfigStrategy] Writing configurations to file ... | Indicates that the configuration data is being written to a file. |
| BM9401 | INFO | [WatchdogConfigStrategy] Starting to load configurations ... | Indicates that the configuration loading process has begun using the WatchdogConfigStrategy. |
| BM9402 | ERROR | [WatchdogConfigStrategy] Configuration validation failed: {e} | Indicates an error during the configuration validation process. |
| BM9402 | ERROR | [WatchdogConfigStrategy] Could not load configuration successfully | Indicates an error occurred while loading the configuration in the WatchdogConfigStrategy. |
| BM1001 | INFO | Launcher initialized with installed browsers. | Logs the initialization of the Launcher with the list of installed browsers. |
| BM3001 | INFO | Launching {browser.upper()} reader | Logs the beginning of the process to launch a reader for a specified browser. |
| BM3002 | INFO | Launched {browser.upper()} reader with PID: {process.pid} | Logs successful launch of the reader process for a specified browser, including the process ID. |
| BM3003 | INFO | Acquiring lock for launch operation | Logs the acquisition of a lock prior to launching a browser reader, ensuring thread safety. |
| BM3004 | INFO | Stopping all readers and releasing lock... | Logs the stopping of all browser reader processes and the release of the shared lock. |
| BM4001 | WARNING | Unsupported browser: {browser} | Logs a warning if a launch attempt is made for a browser that is not supported or not configured properly. |
| BM4002 | WARNING | Requested browser {browser} is not installed on the system. | Logs a warning when an attempt is made to launch a browser that is not installed on the system. |
| BM4003 | ERROR | No browsers to launch. Ensure the desired browsers are installed and try again. | Logs an error when there are no valid browsers to launch due to either configuration issues or installation status. |
| BM4004 | ERROR | An error occurred while launching browsers: {e} | Logs an error with details if an exception occurs during the browser launching process. |
| BM1001 | INFO | Handler class initialized. | Logs the initialization of the Handler class with settings for log rotation and file management. |
| BM1002 | INFO | Defined file paths for logging. | Logs the completion of defining the file paths where logs will be written, depending on the system platform. |
| BM2001 | INFO | Backup count is set to 0, so no rotation will be performed | Logs that no file rotation will occur because the backup count is set to zero. |
| BM2002 | INFO | Handler class invoked | Logs the invocation of the Handler class, indicating that log file management operations are about to start. |
| BM2003 | INFO | Running the scheduled jobs: rollover (function) for duration: {self.rotation} | Logs the setup of scheduled jobs for file rotation based on a specified interval. |
| BM2004 | INFO | File path to rotate {file_paths[browser]} | Logs which file path is set up for rotation in the background job scheduler. |
| BM3001 | INFO | Scheduler information: | Logs general information about the current state of the job scheduler. |
| BM3002 | INFO | Job ID: {job.id}, Next Run Time: {next_run_time} | Logs detailed information for each job in the scheduler, including IDs and next run times. |
| BM3003 | INFO | Rotation is set for {self.rotation} | Logs the setup of the file rotation with the specified interval in seconds. |
| BM3004 | INFO | Background job scheduled for file rotation. | Logs that a background job has been successfully scheduled to handle file rotation. |
| BM9008 | ERROR | eti : {e} | Logs the error faced while getting index |
| BM8001 | INFO | Cache Manager initialized with max entries: {max_entries} | Log indicates that the Cache Manager has been successfully initialized with a specified maximum number of entries. |
| BM8002 | DEBUG | Cache maintenance schedule setup | Log indicates that the cache maintenance schedule has been successfully set up. |
| BM8003 | DEBUG | Cache size ({current_count}) within limits, no cleanup needed | Log indicates that the current cache size is within the acceptable limits, meaning no cleanup is necessary. |
| BM8005 | INFO | Removed {removed_expired} expired and {removed_old} old entries. Current size: {len(self.shared_cache)} | Log indicates that the expired and old cache entries have been removed successfully, with the number of removed entries (removed_expired and removed_old) logged along with the current cache size. |
| BM8006 | INFO | Removed {removed_expired} expired entries. Current size: {len(self.shared_cache)} | Log indicates that the expired cache entries have been successfully removed, with the number of removed entries (removed_expired) logged, along with the current cache size. |
| BM8007 | ERROR | Cache cleanup failed: {e} | Log indicates that the cache cleanup process has failed, and the specific error message is captured by {e}. |
| BM1020 | INFO | Controller interrupted: {e} | The controller was interrupted by a KeyboardInterrupt or an exception, triggering an emergency shutdown. |
| BM1012 | INFO | Browsermon Started in {BROWSERMON_ENV} mode, version: {VERSION} | Logs startup environment mode and Browsermon version. |
| BM1013 | INFO | Running From: {BROWSERMON_DIR} | Logs the directory from which Browsermon is running. |
| BM1013 | INFO | Main process id: {os.getpid()} | Logs the main process ID of the controller. |
| BM1014 | INFO | System UUID: {self.controller_guid} | Logs the system UUID used by the controller for identification. |
| BM3029 | ERROR | State machine error: {e} | An error occurred while executing the state machine, forcing a transition to the ErrorState. |
| BM2010 | INFO | State machine completed | The state machine finished execution successfully. |
| BM3030 | WARNING | Performing emergency shutdown | The controller is performing an emergency shutdown procedure. |
| BM3031 | ERROR | Error during emergency shutdown: {e} | An exception occurred during the emergency shutdown process. |
| BM3030 | ERROR | Failed to start BrowserMonitor | BrowserMonitor failed to start after initialization. |
| BM2011 | INFO | BrowserMonitor initialized successfully | BrowserMonitor started and initialized properly. |
| BM3031 | ERROR | BrowserMonitor initialization failed: {e} | An exception occurred during BrowserMonitor initialization. |
| BM3015 | ERROR | Cannot initialize handler without browser monitor | Handler cannot be created because BrowserMonitor is not initialized. |
| BM3016 | ERROR | Missing required options for handler: {required_keys} | Required options for handler initialization were missing. |
| BM1013 | INFO | Handler initialized successfully | Handler initialized with provided configuration. |
| BM3017 | ERROR | Failed to initialize handler: {e} | Exception occurred during handler initialization. |
| BM3020 | WARNING | Browser monitor thread has died | BrowserMonitor thread is no longer alive. |
| BM3021 | WARNING | Browser monitor has no active processors | BrowserMonitor has no running processors. |
| BM3022 | ERROR | Error checking browser monitor health: {e} | Exception occurred while checking BrowserMonitor health. |
| BM1014 | INFO | Restarting browser monitor | Restarting the BrowserMonitor service. |
| BM3023 | ERROR | Browser monitor failed during restart: {e} | Exception occurred while BrowserMonitor was restarting in background thread. |
| BM1015 | INFO | Browser monitor restarted successfully | BrowserMonitor restarted and running correctly. |
| BM3024 | ERROR | Failed to restart browser monitor: {e} | Exception occurred while restarting BrowserMonitor. |
| BM1016 | INFO | Browser monitor stopped | BrowserMonitor was stopped successfully. |
| BM3025 | ERROR | Error stopping browser monitor: {e} | Exception occurred when stopping BrowserMonitor. |
| BM1018 | INFO | Cleaning up all components... | Cleanup process for all components started. |
| BM1019 | INFO | All components cleaned up | Cleanup process completed successfully. |
| BM9401 | DEBUG | Converting controller configuration to BrowserMonitor configuration | Debug log before starting the conversion of controller options into BrowserMonitor config. |
| BM9401 | INFO | Successfully converted controller configuration to BrowserMonitor configuration | Conversion of controller options into BrowserMonitor config completed successfully. |
| BM9402 | ERROR | Failed to convert configuration: {e} | An exception occurred during configuration conversion, preventing BrowserMonitor config creation. |
| BM3995 | WARNING | Invalid time format: {time_str}, using default 3600s | Time string could not be parsed, defaulting to 3600 seconds. |
| BM3018 | ERROR | Failed to initialize health checker: {e} | Error occurred during health checker initialization. |
| BM3019 | ERROR | Health checker not initialized | Attempted to start monitoring without initializing the health checker. |
| BM3020 | ERROR | Failed to start health monitoring: {e} | Exception occurred when starting health monitoring. |
| BM3026 | WARNING | Browser monitor is unhealthy | The browser monitor was detected as unhealthy. |
| BM1020 | INFO | Attempting to restart browser monitor (attempt {n}) | Health manager attempting to restart the browser monitor due to unhealthy state. |
| BM1021 | INFO | Browser monitor restarted successfully | Restart attempt for browser monitor succeeded. |
| BM3027 | ERROR | Failed to restart browser monitor | Restart attempt for browser monitor failed. |
| BM3028 | ERROR | Maximum restart attempts reached for browser monitor | Browser monitor restart attempts exceeded allowed retries. |
| BM3029 | ERROR | Error checking browser monitor health: {e} | Exception occurred while checking the health of browser monitor. |
| BM3010 | FATAL | Could not read server configuration; Check watchdog ip and port settings | Indicates that the server configuration could not be loaded, likely due to invalid or missing IP/port values. |
| BM9401 | INFO | Loaded server conf: {server_conf} | Successfully loaded server configuration values. |
| BM9401 | INFO | Loaded elastic conf: {self.es_conf} | Successfully loaded elasticsearch configuration values. |
| BM3011 | FATAL | Could not load configurations successfully | Indicates that the main configuration could not be retrieved from the config provider. |
| BM3013 | ERROR | Failed to load configurations: {e} | Captures any unexpected exception that occurs during the configuration loading process. |
| BM3012 | FATAL | Configuration validation failed: {error_message} | Configuration options failed validation and corrections could not be applied. |
| BM3985 | DEBUG | Manual rotation of history files called | Indicates that a manual rotation process for browser history files was requested. |
| BM3986 | INFO | History files already rotated (marker file present); skipping | Rotation skipped because a marker file indicates rotation has already been performed for this version. |
| BM3990 | ERROR | Manual rotation failed: {e} | An exception occurred during manual rotation, stopping the process. |
| BM3987 | ERROR | Missing required rotation options: {missing_keys} | One or more required configuration options (logdir, backup_count) were missing. |
| BM3987 | ERROR | Log directory not set in configuration | The logdir option is empty or invalid, preventing rotation. |
| BM3991 | DEBUG | Successfully rotated {filename} | A browser history file was successfully rotated. |
| BM3989 | ERROR | Failed to rotate {filename}: {e} | An error occurred while rotating a specific file. |
| BM3992 | DEBUG | File {filename} does not exist, skipping rotation | A file from the default rotation list does not exist and is skipped. |
| BM3993 | DEBUG | Created rotation marker file: {marker_file} | Successfully created a marker file to indicate that rotation was completed for this version. |
| BM3988 | ERROR | Failed to create marker file: {e} | An exception occurred while attempting to create the marker file. |
| BM2001 | INFO | Controller entering initialization state | Controller begins initialization sequence. |
| BM3023 | ERROR | Initialization failed: {e} | An exception occurred while initializing controller components. |
| BM2002 | DEBUG | Exiting initialization state | Initialization state exited. |
| BM2003 | INFO | Controller entering running state | Controller has transitioned into running state. |
| BM3024 | WARNING | BrowserMonitor is not healthy | Health check detected that BrowserMonitor is not functioning correctly. |
| BM3025 | ERROR | Error in running state: {e} | Error occurred while handling running state logic. |
| BM1016 | INFO | Configuration changed, reinitializing | Detected a configuration change; components will be reinitialized. |
| BM2011 | INFO | Components reinitialized successfully | Reinitialization of BrowserMonitor and Handler completed successfully. |
| BM1017 | DEBUG | Configuration unchanged | Configuration has not changed since last check. |
| BM3026 | ERROR | Configuration check failed: {e} | Error occurred while validating or applying configuration changes. |
| BM2004 | DEBUG | Exiting running state | Controller leaves running state. |
| BM2005 | INFO | Controller entering stopping state | Controller begins shutdown process. |
| BM2006 | INFO | Controller stopped successfully | Controller stopped all components and completed shutdown. |
| BM3027 | ERROR | Error during shutdown: {e} | An error occurred while stopping components during shutdown. |
| BM2007 | DEBUG | Exiting stopping state | Shutdown process exited. |
| BM2008 | ERROR | Controller entering error state: {self.error_message} | Controller transitioned into error state due to a critical issue. |
| BM3028 | FATAL | Fatal error occurred: {self.error_message} | A fatal error was encountered; transitioning to StoppingState. |
| BM2009 | DEBUG | Exiting error state | Error state exited. |
| BM6410 | ERROR | Error monitoring resources: {e} | Logged when an exception occurs while collecting CPU/memory usage statistics. |
| BM6411 | INFO | Prometheus metrics server started on port {self.port} | Indicates that the Prometheus HTTP server successfully started. |
| BM6412 | INFO | Metrics available at http://localhost:{self.port}/metrics | Provides the local URL where metrics can be scraped. |
| BM6413 | ERROR | Failed to start Prometheus HTTP server: {e} | Logged when the Prometheus HTTP server cannot be started due to an exception. |
| BM6415 | ERROR | Error handling Prometheus metric update: {e} | Captures unexpected errors while processing or updating Prometheus metrics. |
| BM6417 | INFO | Prometheus metrics subscriber shutting down | Indicates that the metrics subscriber is shutting down gracefully. |
| BM6010 | INFO | Incremental run: fetching data newer than {since_timestamp} | Indicates that the adapter is performing an incremental history fetch, retrieving entries after the provided timestamp. |
| BM6011 | INFO | First run for profile {profile.name}: fetching ALL history data | Logged when no prior timestamp is provided, meaning all available history entries will be fetched. |
| BM6012 | INFO | First run: Retrieved {len(results)} total history entries for profile {profile.name} | Confirms the number of history entries retrieved during the first full run for a given profile. |
| BM6013 | INFO | Incremental: Retrieved {len(results)} new entries for profile {profile.name} | Confirms the number of new history entries retrieved during an incremental run. |
| BM6014 | ERROR | Error processing {self._browser_config.name} history file {history_path}: {e} | Logged when an exception occurs while copying or reading the Chromium history database file. |
| BM6020 | ERROR | Failed to discover users: {e} | Logged when system user discovery fails due to an exception. |
| BM6021 | WARN | Skipping inaccessible user directory: {user.username} | Indicates that a discovered system user directory is inaccessible and skipped. |
| BM6022 | ERROR | Error getting profiles for user {user.username}: {e} | Logged when profile retrieval for a specific user fails. |
| BM6023 | ERROR | Error getting history from profile {profile.name}: {e} | Logged when history collection from a specific profile fails. |
| BM6024 | ERROR | Could not determine user for profile {profile.name} at {profile.path} | Indicates that no matching user could be mapped to the given profile path. |
| BM6025 | ERROR | Could not create browser instance for user {user.username} | Logged when the adapter cannot create a browser instance for a discovered user. |
| BM6026 | ERROR | Error getting history paths for profile {profile.name}: {e} | Logged when history file paths cannot be retrieved for a profile. |
| BM6027 | DEBUG | History file does not exist: {history_path} | Indicates that the expected history database file for a profile is missing. |
| BM6028 | DEBUG | Processing history file: {history_path} with timestamp filter: {since_timestamp} | Logged before processing a history file, showing path and applied timestamp filter (if any). |
| BM6029 | ERROR | Error processing history file for profile {profile.name}: {e} | Logged when an unexpected exception occurs during processing of a profile’s history file. |
| BM6030 | ERROR | Error getting {self._browser_config.name} profiles for user {user.username}: {e} | Logged when fetching browser profiles for a specific user fails. |
| BM6031 | ERROR | Error getting {self._browser_config.name} profiles: {e} | Logged when fetching profiles for the current user fails. |
| BM6060 | INFO | Firefox incremental run: fetching data newer than {since_timestamp} | Logged during incremental run, fetching only history entries newer than the last processed timestamp. |
| BM6061 | INFO | Firefox first run for profile {profile.name}: fetching ALL history data | Logged during first run, fetching all available Firefox history data for the specified profile. |
| BM6062 | INFO | Firefox first run: Retrieved {len(results)} total history entries | Logged after first run, showing the total number of retrieved Firefox history entries. |
| BM6063 | INFO | Firefox incremental: Retrieved {len(results)} new entries | Logged after incremental run, showing the count of newly retrieved Firefox history entries. |
| BM6064 | ERROR | Error processing Firefox history file {history_path}: {e} | Logged when an exception occurs during the processing of a Firefox history file. |
| BM6070 | ERROR | Error getting {self._browser_config.name} profiles: {e} | Logged when an exception occurs while retrieving Chromium browser profiles. |
| BM6071 | ERROR | Error processing {self._browser_config.name} history file {history_path}: {e} | Logged when an exception occurs while processing a Chromium history file for a given profile. |
| BM6074 | ERROR | Error getting Firefox profiles: {e} | Logged when fetching Firefox profiles fails. {e} contains the exception message. |
| BM6073 | ERROR | Error processing Firefox history file {history_path}: {e} | Logged when reading/parsing a Firefox history SQLite file fails. {history_path} is the file path, {e} is the error. |
| BM6080 | DEBUG | No extensions directory found for Chrome profile {profile.name} (user: {user.username}) | Logged when no Chrome extensions directory exists for a specific profile with user context. |
| BM6081 | INFO | Scanning Chrome extensions for user {user.username} in {extensions_path} | Logged when starting to scan Chrome extensions for a specific user. |
| BM6082 | ERROR | Error scanning Chrome extensions directory {extensions_path} for user {user.username}: {e} | Logged when scanning Chrome extensions for a user fails. {e} contains the exception details. |
| BM6083 | DEBUG | No extensions directory found for Chrome profile {profile.name} | Logged when no Chrome extensions directory exists for a single-user profile. |
| BM6084 | INFO | Scanning Chrome extensions in {extensions_path} | Logged when starting to scan Chrome extensions for a single-user profile. |
| BM6085 | ERROR | Error scanning Chrome extensions directory {extensions_path}: {e} | Logged when scanning Chrome extensions in a single-user profile fails. {e} contains the exception. |
| BM6086 | DEBUG | No manifest.json found for extension {extension_id} (user: {user.username}) | Logged when manifest.json is missing for a specific extension in a multi-user context. |
| BM6087 | INFO | Found Chrome extension for user {user.username}: {extension_name} (ID: {extension_id}) | Logged when a Chrome extension is successfully discovered for a user. |
| BM6088 | ERROR | Error processing Chrome extension {extension_id} for user {user.username}: {e} | Logged when processing a Chrome extension fails for a specific user. {e} contains the error message. |
| BM6089 | DEBUG | No manifest.json found for extension {extension_id} | Logged when manifest.json is missing for a specific extension in single-user context. |
| BM6090 | INFO | Found Chrome extension: {extension_name} (ID: {extension_id}) | Logged when a Chrome extension is successfully discovered for a single-user profile. |
| BM6091 | ERROR | Error processing Chrome extension {extension_id}: {e} | Logged when processing a Chrome extension fails in single-user context. {e} contains the error message. |
| BM6092 | DEBUG | Could not load messages from {message_file}: {e} | Logged when localized messages could not be loaded from a manifest messages.json file. {e} gives the error. |
| BM6093 | DEBUG | Could not get install date for {extension_dir}: {e} | Logged when the install date of an extension cannot be determined. {e} contains the exception. |
| BM6094 | DEBUG | Skipping inaccessible user directory for extensions: {user.username} | Logged when a system user directory is inaccessible and is skipped during extension discovery. |
| BM6095 | ERROR | Error discovering extensions for user {user.username}: {e} | Logged when extension discovery fails for a specific user. {e} contains the exception details. |
| BM6096 | ERROR | Failed to discover users for extensions: {e} | Logged when the system user discovery process fails. {e} contains the exception details. |
| BM6097 | DEBUG | No {browser_key} profiles found for user {user.username} | Logged when no browser profiles are found for a specific user. |
| BM6098 | ERROR | Error discovering extensions for profile {profile.name} (user: {user.username}): {e} | Logged when extension discovery fails for a specific browser profile under a user. {e} contains the error. |
| BM6099 | ERROR | Error getting profiles for user {user.username}: {e} | Logged when retrieval of browser profiles fails for a specific user. {e} contains the exception details. |
| BM6190 | DEBUG | No {browser_key} profiles found for user {user.username} | Logged when a user does not have any profiles for the given browser. (Normal case, not always an error.) |
| BM6191 | DEBUG | Found {len(profiles)} {browser_key} profiles for user {user.username} | Logged when browser profiles are successfully discovered for a specific user. |
| BM6192 | DEBUG | Error getting {browser_key} profiles for user {user.username}: {e} | Logged when an error occurs while retrieving profiles for a user. {e} contains the exception details. |
| BM6193 | ERROR | Error discovering extensions for current user: {e} | Logged when fallback extension discovery for the current user fails. {e} contains the exception details. |
| BM6194 | ERROR | Error getting original {browser_key} profiles: {e} | Logged when retrieval of browser profiles fails for the original (non-multi-user) browser instance. {e} gives error. |
| BM6195 | ERROR | Error discovering extensions for profile {profile.name}: {e} | Logged when extension discovery fails for a given profile (either multi-user or single-user). {e} contains details. |
| BM6210 | DEBUG | No extensions directory found for Firefox profile {profile.name} (user: {user.username}) | Logged when the Firefox profile does not contain an extensions directory for a multi-user profile. |
| BM6211 | INFO | Scanning Firefox add-ons for user {user.username} in {extensions_path} | Logged when scanning begins for Firefox add-ons in a user’s profile directory. |
| BM6212 | ERROR | Error scanning Firefox extensions directory {extensions_path} for user {user.username}: {e} | Logged when scanning a user’s Firefox extensions directory fails with an exception. |
| BM6213 | DEBUG | No extensions directory found for Firefox profile {profile.name} | Logged when the Firefox profile does not contain an extensions directory for a single-user profile. |
| BM6214 | INFO | Scanning Firefox add-ons in {extensions_path} | Logged when scanning begins for Firefox add-ons in a single-user profile directory. |
| BM6215 | ERROR | Error scanning Firefox extensions directory {extensions_path}: {e} | Logged when scanning a single-user Firefox extensions directory fails with an exception. |
| BM6216 | DEBUG | No manifest.json found for Firefox addon {addon_dir.name} (user: {user.username}) | Logged when a directory-based add-on for a multi-user profile does not have a manifest.json. |
| BM6217 | INFO | Found Firefox add-on for user {user.username}: {extension_name} (ID: {addon_id}) | Logged when a directory-based Firefox add-on is successfully discovered for a multi-user profile. |
| BM6218 | ERROR | Error processing Firefox addon directory {addon_dir} for user {user.username}: {e} | Logged when processing a directory-based add-on for a multi-user profile fails with an exception. |
| BM6219 | DEBUG | No manifest.json found for Firefox addon {addon_dir.name} | Logged when a directory-based add-on for a single-user profile does not have a manifest.json. |
| BM6220 | INFO | Found Firefox add-on: {extension_name} (ID: {addon_id}) | Logged when a directory-based Firefox add-on is successfully discovered in a single-user profile. |
| BM6221 | ERROR | Error processing Firefox addon directory {addon_dir}: {e} | Logged when processing a directory-based add-on for a single-user profile fails with an exception. |
| BM6222 | INFO | Found Firefox add-on (XPI) for user {user.username}: {extension_name} (ID: {addon_id}) | Logged when a packaged add-on (.xpi) is successfully discovered in a multi-user profile. |
| BM6223 | DEBUG | No manifest.json found in {xpi_path} for user {user.username}, skipping | Logged when an .xpi add-on does not contain a manifest.json in a multi-user profile. |
| BM6224 | ERROR | Error processing Firefox XPI addon {xpi_path} for user {user.username}: {e} | Logged when processing a packaged add-on (.xpi) for a multi-user profile fails with an exception. |
| BM6225 | INFO | Found Firefox add-on (XPI): {extension_name} (ID: {addon_id}) | Logged when a packaged add-on (.xpi) is successfully discovered in a single-user profile. |
| BM6226 | DEBUG | No manifest.json found in {xpi_path}, skipping | Logged when an .xpi add-on does not contain a manifest.json in a single-user profile. |
| BM6227 | ERROR | Error processing Firefox XPI addon {xpi_path}: {e} | Logged when processing a packaged add-on (.xpi) for a single-user profile fails with an exception. |
| BM6228 | DEBUG | Could not read Firefox addons.json: {e} | Logged when the addons.json metadata file cannot be read or parsed. |
| BM6229 | DEBUG | Could not get install date for {path}: {e} | Logged when the system cannot retrieve the install date for a given add-on path. |
| BM6330 | DEBUG | No extensions directory found for Edge profile {profile.name} (user: {user.username}) | Logged when the Edge profile does not contain an Extensions directory for a multi-user profile. |
| BM6331 | INFO | Scanning Edge extensions for user {user.username} in {extensions_path} | Logged when scanning begins for Edge extensions in a multi-user profile directory. |
| BM6332 | ERROR | Error scanning Edge extensions directory {extensions_path} for user {user.username}: {e} | Logged when scanning a user’s Edge extensions directory fails with an exception. |
| BM6333 | DEBUG | No extensions directory found for Edge profile {profile.name} | Logged when the Edge profile does not contain an Extensions directory for a single-user profile. |
| BM6334 | INFO | Scanning Edge extensions in {extensions_path} | Logged when scanning begins for Edge extensions in a single-user profile directory. |
| BM6335 | ERROR | Error scanning Edge extensions directory {extensions_path}: {e} | Logged when scanning a single-user Edge extensions directory fails with an exception. |
| BM3053 | DEBUG | Using cached timestamp {last_timestamp} for profile {profile.name} | Logged when cached timestamp is found and used for optimized history retrieval. |
| BM3054 | DEBUG | No cache found for profile {profile.name}, fetching recent history | Logged when no cache exists and recent history must be fetched from the database. |
| BM3055 | INFO | Loaded {len(entries)} entries for profile {profile.name} (after SQL filtering) | Logged after history entries are loaded for a profile using SQL-level filtering. |
| BM3056 | INFO | No new entries to process for profile {profile.name} | Logged when no new entries are found for a profile. |
| BM3057 | INFO | Processing {len(new_entries)} new entries for profile {profile.name} | Logged when new entries are identified and will be processed. |
| BM3058 | ERROR | Error classifying entries for profile {profile.name}: {e} | Logged when classification of history entries fails for a profile. |
| BM3058 | WARNING | No entries to output for profile {profile.name} | Logged when no entries are available to output for a profile after filtering and classification. |
| BM3059 | ERROR | Error processing profile {profile.name}: {e} | Logged when processing a specific profile fails due to an exception. |
| BM3064 | INFO | Completed processing {browser_name}: {len(all_entries)} entries from {len(profiles)} profiles in {duration:.2f}s | Logged after all profiles for a browser are processed successfully with stats on entries and duration. |
| BM3065 | ERROR | Fatal error in processing {browser_name}: {e} | Logged when a fatal error occurs in processing the browser history, halting the process. |
| BM6400 | ERROR | Error in extension discovery: {error} | An exception occurred during extension discovery; details are logged. |
| BM6420 | DEBUG | Subscribed {subscriber_class} to {event_count} event types | A subscriber was successfully registered for one or more event types. |
| BM6421 | DEBUG | Published {event_type} event to {subscriber_count} subscribers | An event was published to the specified number of subscribers. |
| BM6422 | ERROR | Error in event subscriber {subscriber_class}: {error} | An exception occurred while handling an event in a subscriber. |
| BM6423 | INFO | EventPublisher shutdown complete | EventPublisher was successfully shut down and resources released. |
| BM6424 | INFO | Kafka publisher initialized: server={kafka_server}, topic={topic} | KafkaPublisher was successfully initialized with the provided server/topic. |
| BM6425 | ERROR | Failed to initialize Kafka producer: {error} | An error occurred during Kafka producer initialization. |
| BM6426 | DEBUG | Published entry to Kafka: topic={topic}, partition={partition}, offset={offset} | A single history entry was successfully published to Kafka. |
| BM6427 | ERROR | Kafka error publishing entry: {error} | A Kafka-related error occurred when publishing a history entry. |
| BM6428 | ERROR | Error publishing entry to Kafka: {error} | A general error occurred while publishing a history entry. |
| BM6430 | INFO | Published {success_count} entries to Kafka (failed: {failed_count}) | Multiple entries were published to Kafka with success and failure counts. |
| BM6431 | ERROR | Error sending entry in batch: {error} | An error occurred while sending a single entry within a batch. |
| BM6432 | DEBUG | Published batch {batch_number}: {entry_count} entries | A batch of entries was successfully published to Kafka. |
| BM6433 | ERROR | Error flushing Kafka producer: {error} | An error occurred during Kafka producer flush operation. |
| BM6434 | INFO | Kafka publisher closed: {published_count} messages published, {failed_count} failed | KafkaPublisher was closed with summary of published and failed messages. |
| BM6435 | ERROR | Error closing Kafka producer: {error} | An error occurred while closing the Kafka producer. |
| BM6460 | INFO | Started processing {browser} browser with {profile_count} profiles | Extension discovery process started for the given browser with the number of profiles. |
| BM6461 | INFO | Completed processing {browser} - {entries_processed} entries, {profiles_processed} profiles in {duration}s | Extension discovery completed with summary of entries, profiles, and execution duration. |
| BM6462 | ERROR | Failed to process {browser}: {error} | An error occurred during extension discovery for the specified browser. |
| BM6463 | ERROR | Error [{error_type}]: {error_message} | A generic error event was published and logged with error type and message. |
| BM6464 | DEBUG | Event: {event_type} - {data} | Debug logging of any additional events when log_all_events=True. |
| BM6465 | ERROR | Failed to publish entry to Kafka: {error} | Error occurred while publishing a single entry to Kafka. |
| BM6466 | DEBUG | Published {entry_count} entries to Kafka topic '{topic}' | Successfully published entries to Kafka with topic name. |
| BM6467 | INFO | {browser} progress: {processed_profiles}/{total_profiles} profiles ({percentage}%) - {total_entries} entries | Logs ongoing processing progress of profiles and entries with percentage completion. |
| BM6468 | INFO | {browser} completed: {processed_profiles} profiles, {total_entries} entries in {duration}s | Logs final processing completion summary including duration. |
| BM6470 | ERROR | Failed to write event to file {output_file}: {error} | Error occurred while writing an event to the configured output file. |
| BM5080 | WARNING | Unknown cache type '{cache_type}', using file cache | When an unrecognized cache type is specified, the system falls back to the file cache method. |
| BM5070 | INFO | Created shared classification cache manager: max_size={cache_max_size}, ttl={cache_ttl}s | Indicates that a shared classification cache manager was successfully created with configured size and TTL. |
| BM4050 | DEBUG | Loaded {browser} cache with {count} profiles | Successfully loaded cache file for the given browser with number of profiles. |
| BM4051 | ERROR | Error loading {browser} cache: {error} | Failed to load cache file for the given browser; cache initialized as empty. |
| BM4052 | DEBUG | Saved {browser} cache to {cache_path} | Successfully saved cache data for the given browser to disk. |
| BM4053 | ERROR | Error saving {browser} cache: {error} | Failed to save cache data for the given browser to disk. |
| BM4054 | DEBUG | Updated cache for {browser_type} profile {profile.name} with {count} entries | Updated cache with the latest processed entries for the given browser profile. |
| BM4055 | INFO | Cleaned up {cleaned_count} old cache entries | Removed expired or outdated profile cache entries. |
| BM4060 | DEBUG | Memory cache filtered {original_count} to {new_count} new entries | Memory cache reduced the number of entries by filtering already processed ones. |
| BM4061 | DEBUG | Updated memory cache for profile {profile.name} | Memory cache updated with the latest entries for the given profile. |
| BM4062 | DEBUG | Cleaned up {removed_count} LRU cache entries | Removed least recently used entries from memory cache to maintain size limits. |
| BM4063 | DEBUG | Found timestamp in memory cache for profile {profile.name}: {timestamp} | Memory cache returned a valid timestamp for the given profile. |
| BM4064 | DEBUG | Found timestamp in file cache for profile {profile.name}: {timestamp} | File cache returned a valid timestamp for the given profile; memory warmed up with this value. |
| BM4065 | DEBUG | No cached timestamp found for profile {profile.name} | No timestamp found in memory or file cache for the given profile. |
| BM4066 | DEBUG | File cache provided more restrictive filtering for {profile.name} | File cache filtering reduced entries more effectively than memory cache for this profile. |
| BM4067 | DEBUG | Updated memory cache for profile {profile.name} | Memory cache successfully updated during hybrid strategy update. |
| BM4068 | ERROR | Error updating memory cache for profile {profile.name}: {error} | Failed to update memory cache for the given profile in hybrid strategy. |
| BM4069 | DEBUG | Updated file cache for profile {profile.name} | File cache successfully updated during hybrid strategy update. |
| BM4070 | ERROR | Error updating file cache for profile {profile.name}: {error} | Failed to update file cache for the given profile in hybrid strategy. |
| BM4082 | DEBUG | Cleaned up memory cache | Expired entries removed from memory cache during cleanup. |
| BM4083 | ERROR | Error cleaning memory cache: {error} | Exception occurred while cleaning memory cache. |
| BM4084 | DEBUG | Cleaned up file cache | Expired entries removed from file cache during cleanup. |
| BM4085 | ERROR | Error cleaning file cache: {error} | Exception occurred while cleaning file cache. |
| BM4086 | DEBUG | Warmed memory cache for profile {profile.name} with timestamp {timestamp} | Memory cache populated using data from file cache (cache warmup). |
| BM4087 | DEBUG | Failed to warm memory cache for profile {profile.name}: {error} | Error occurred while attempting to warm up memory cache from file cache. |
| BM4088 | DEBUG | File cache disabled, skipping sync | Synchronization skipped because file cache is disabled in hybrid strategy. |
| BM4089 | INFO | Synchronized {count} profiles from file cache to memory cache | Memory cache updated with profiles and timestamps from file cache. |
| BM4090 | ERROR | Error during cache synchronization: {error} | Exception occurred during synchronization between memory and file caches. |
| BM5010 | DEBUG | ETI Classification: {cached_count} cached, {to_classify_count} to classify | Logs how many URLs were found in ETI cache vs. how many need classification. |
| BM5011 | DEBUG | UCS Classification: {cached_count} cached, {to_classify_count} to classify | Logs how many domains were found in UCS cache vs. how many need classification. |
| BM5013 | DEBUG | Joint Classification - ETI: {cached_count} cached, {to_classify_count} to classify | Logs ETI side of joint classification, showing cached vs. to-be-classified URL counts. |
| BM5014 | DEBUG | Joint Classification - UCS: {cached_count} cached, {to_classify_count} to classify | Logs UCS side of joint classification, showing cached vs. to-be-classified domain counts. |
| BM1040 | INFO | BrowserMonitor initializing | Indicates that BrowserMonitor initialization has started. |
| BM1041 | INFO | Created processor for {browser} | Successfully created a processor for the specified browser. |
| BM1042 | INFO | Created extension processor for {browser} | Successfully created an extension processor for the specified browser. |
| BM1043 | WARNING | Extension processor not available for {browser}: {e} | Extension processor creation failed for a browser; logs reason. |
| BM1044 | ERROR | Failed to create processor for {browser}: {e} | Processor creation failed for a specific browser; logs error message. |
| BM1045 | ERROR | No processors were created successfully | No processors could be created; system cannot start monitoring. |
| BM1046 | INFO | Browser monitoring service started successfully | Browser monitoring service started without errors. |
| BM1046 | ERROR | Failed to start browser monitoring: {e} | Service startup failed due to an exception. |
| BM1047 | INFO | Stopping browser monitoring service | Service shutdown sequence started. |
| BM1048 | INFO | Browser monitoring service stopped | Service shutdown completed successfully. |
| BM1048 | ERROR | Error stopping browser monitoring: {e} | Error occurred during shutdown process. |
| BM1050 | INFO | Starting browser monitoring | Explicit request to start browser monitoring. |
| BM1051 | INFO | Created processor for {browser} | Logs processor creation (used in start_monitoring). |
| BM1052 | ERROR | Failed to create processor for {browser}: {e} | Logs processor creation failure (used in start_monitoring). |
| BM1053 | DEBUG | No extension processors available | Logs when extension discovery is attempted but no extension processors exist. |
| BM1054 | DEBUG | {browser} extension discovery completed: {result.extensions_found} extensions found | Extension discovery completed successfully with number of extensions found. |
| BM1055 | ERROR | Error discovering extensions for {browser}: {e} | Extension discovery failed for a specific browser. |
| BM1056 | ERROR | Error in _discover_extensions_once: {e} | General error occurred in the extension discovery cycle. |
| BM1056 | WARNING | No processors available for processing | Warning issued when no processors are available during _process_once. |
| BM1057 | DEBUG | {browser} processing completed: {result} | Logs completion of browser history processing with result summary. |
| BM1058 | ERROR | Error processing {browser}: {e} | Logs failure while processing history for a specific browser. |
| BM1059 | INFO | Status: {status_dict} | Logs overall status of the monitoring service after a processing cycle. |
| BM1060 | ERROR | Error in _process_once: {e} | General error occurred while processing history once. |
| BM1070 | ERROR | Invalid schedule window format: {window} | Logs invalid schedule window string during parsing. |