Types are logged with each log line to categorize the log.
Description: A log that results from a user taking an action, i.e. an election admin uploading an election definition to a machine.
Description: Status update or message that the application took without user action.
Description: A log that results from the system taking some action, i.e. the machine booting.
Description: A log that results from the system updating on the status of a process it is running, i.e. completion of machine shutdown or boot.
Description: Action taken by the votingworks application automatically when a certain condition is met. Example: When a new USB drive is detected, the application will automatically mount it.
IDs are logged with each log to identify the log being written.
Type: user-action
Description: The user has configured current machine to a new election definition.
Machines: All
Type: user-action
Description: The user has unconfigured current machine to remove the current election definition, and all other data.
Machines: All
Type: system-action
Description: The machine is beginning the boot process.
Machines: All
Type: system-status
Description: The machine has completed the boot process.
Machines: All
Type: system-action
Description: The machine is beginning the shutdown process to power down or reboot, as indicated by the message.
Machines: All
Type: system-status
Description: The machine has completed all the steps to shutdown and will now power down or reboot.
Machines: All
Type: system-status
Description: A message from the machine kernel about an externally-connected USB device, usually when a new device is connected or disconnected.
Machines: All
Type: user-action
Description: A user attempted to enter a passcode to log in.
Machines: All
Type: user-action
Description: A user logged out.
Machines: All
Type: user-action
Description: A user attempted to log in. Disposition is success if they logged in, failure if not. An optional reason may be provided.
Machines: All
Type: application-status
Description: USB Drive detected a status update. Potential USB statuses are: notavailable - No USB Drive detection is available, absent - No USB identified, present - USB identified but not mounted, mounted - USB mounted on device, ejecting - USB in the process of ejecting.
Machines: All
Type: user-action
Description: A request to eject the current USB drive was given by the user, the usb drive will now be ejected.
Machines: All
Type: application-status
Description: The current USB drive finished attempting to ejected. Success or failure indicated by disposition.
Machines: All
Type: application-action
Description: The USB Drive is attempting to mount. This action is taken automatically by the application when a new USB drive is detected.
Machines: All
Type: application-status
Description: USB Drive mount has completed. Success or failure is indicated by the disposition.
Machines: All
Type: application-status
Description: Application finished starting up, success or failure indicated by disposition.
Machines: All
Type: application-status
Description: Application saw a printer configuration added to the system, current connection status of that printer is logged.
Machines: All
Type: application-status
Description: Application saw a printer configuration removed from the system.
Machines: All
Type: application-status
Description: Application saw a change to the connection status of a given configured printer.
Machines: All
Type: application-status
Description: Application saw a device attached to the system.
Machines: All
Type: application-status
Description: Application saw a device unattached from the system.
Machines: All
Type: application-action
Description: A piece of information (current election, loaded CVR files, etc.) is loaded from storage. May happen as an automated action when an application starts up, or as a result of a user action.
Machines: All
Type: user-action
Description: A piece of information is saved to storage, usually resulting from a user action for example a user loading CVR files results in those files being saved to storage.
Machines: All
Type: user-action
Description: File is saved to a USB drive. Success or failure indicated by disposition. Type of file specified with "fileType" key. For success logs the saved filename specified with "filename" key.
Machines: All
Type: user-action
Description: Saving the ballot package is initiated.
Machines: vx-admin-frontend
Type: user-action
Description: Saving the ballot package completed, success or failure is indicated by the disposition.
Machines: vx-admin-frontend
Type: user-action
Description: One or more copies of a ballot were printed. Success or failure indicated by the disposition. Precinct, ballot style, ballot type, number of copies and other details included in log data.
Machines: vx-admin-frontend
Type: user-action
Description: Report of all printed ballots was printed. Success or failure indicated by the disposition.
Machines: vx-admin-frontend
Type: user-action
Description: A smartcard is being programmed for a specific user role. The user role is indicated by the programmedUserRole key.
Machines: vx-admin-frontend
Type: user-action
Description: A smartcard has been programmed for a specific user role. The user role is indicated by the programmedUserRole key. Success or failure is indicated by the disposition.
Machines: vx-admin-frontend
Type: user-action
Description: A smartcard is being unprogrammed. The current smartcard user role is indicated by the programmedUserRole key.
Machines: vx-admin-frontend
Type: user-action
Description: A smartcard has been unprogrammed. The previous (or current in the case of failure) smartcard user role is indicated by the previousProgrammedUserRole (or programmedUserRole in the case of failure) key. Success or failure is indicated by the disposition.
Machines: vx-admin-frontend
Type: user-action
Description: Smartcard is programmed to override a flag protecting writes on the card. By default admin cards can not be written unless write protection is first overridden.
Machines: vx-admin-frontend
Type: user-action
Description: User loaded CVR to the machine. Success or failure indicated by disposition.
Machines: vx-admin-frontend
Type: user-action
Description: User opened load CVR modal and usb is searched for possible CVR files to load.
Machines: vx-admin-frontend
Type: user-action
Description: New cast vote record files seen, initiating recomputation of tally data.
Machines: vx-admin-frontend
Type: user-action
Description: Tally recomputed with new cast vote record files, success or failure indicated by disposition.
Machines: vx-admin-frontend
Type: user-action
Description: User loaded external tally file to the machine. File type indicated by fileType key. Success or failure indicated by disposition.
Machines: vx-admin-frontend
Type: user-action
Description: User added or edited manually entered tally data to be included alongside loaded Cvr files.
Machines: vx-admin-frontend
Type: user-action
Description: User marked the tally results as official. This disabled loading any more cvr or other tally data files.
Machines: vx-admin-frontend
Type: user-action
Description: The user removed Cvr, External Tally data, manually entered tally data, or all tally data. The type of file removed specified by the filetype key.
Machines: vx-admin-frontend
Type: user-action
Description: Tally Report previewed and viewed in the app.
Machines: vx-admin-frontend
Type: user-action
Description: Tally Report printed.
Machines: vx-admin-frontend
Type: user-action
Description: Initiating conversion of tally results to SEMS file format.
Machines: vx-admin-frontend
Type: user-action
Description: User printed the test deck. Success or failure indicated by disposition.
Machines: vx-admin-frontend
Type: user-action
Description: User printed the test deck tally report. Success or failure indicated by disposition.
Machines: vx-admin-frontend
Type: user-action
Description: User has initiated toggling between test mode and live mode in the current application.
Machines: All
Type: user-action
Description: User has finished toggling between live mode and test mode in the given application. Success or failure is indicated by the disposition.
Machines: All
Type: user-action
Description: User has initiated clearing ballot data in the current application.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: User has finished clearing ballot data in the given application. Success or failure is indicated by the disposition.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: User has initiated overriding the thresholds of when to count marks seen by the scanning module. New mark thresholds specified in the keys marginal definite and, if defined, writeInText.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: User has finished overriding the thresholds of when to count marks seen by the scanning module. Success or failure is indicated by the disposition. New mark thresholds specified in the keys marginal definite and, if defined, writeInText.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: User saved a backup file of the scanned ballot image files and CVRs. Success or failure indicated by disposition.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: User had initiated configuring the machine from a ballot package. The ballot package will be loaded from the USB drive, each ballot will be configured, the scanner will be configured, and then the election configuration will be complete.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: List of ballot packages read from usb and displayed to user to load to machine.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: The ballot package has been read from the USB drive. Success or failure indicated by disposition.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: The specified ballot has been configured on the machine. Success or failure indicated by disposition. ballotStyleId, precinctId and isLiveMode keys specify details on the ballot configured.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: The final configuration steps for the scanner for the ballot package have completed. Success or failure indicated by disposition.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: User has initiated saving CVR file to the USB drive.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: User has finished saving a CVR file of all results to the USB drive. Success or failure indicated by disposition. On success, number of ballots included in CVR specified by numberOfBallots.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: user-action
Description: User has initiated deleting a scanning batch. Number of ballots in batch specified by keep numberOfBallotsInBatch. Batch ID specified by batchId
Machines: vx-central-scan-frontend
Type: user-action
Description: User has completed deleting a scanning batch. Number of ballots in batch specified by keep numberOfBallotsInBatch. Batch ID specified by batchId.
Machines: vx-central-scan-frontend
Type: user-action
Description: The user has begun scanning a new batch of ballots. Success or failure of beginning the process of scanning indicated by disposition. Batch ID for next scanned batch indicated in batchId.
Machines: vx-central-scan-frontend
Type: user-action
Description: A single sheet in a batch has completed scanning. Success or failure of the scanning indicated by disposition. Ballots rejected due to being unreadable, configured for the wrong election, needed resolution, etc. marked as failure. Current batch specified by batchId and sheet in batch specified by sheetCount.
Machines: vx-central-scan-frontend
Type: user-action
Description: A batch of scanned sheets has finished scanning. Success or failure indicated by disposition.
Machines: vx-central-scan-frontend
Type: user-action
Description: Scanning continued by user after errors and/or warning stopped scanning. Log will indicate if the sheet was tabulated with warnings, or if the user indicated removing the ballot in order to continue scanning.
Machines: vx-central-scan-frontend
Type: application-status
Description: Information about a ballot sheet that needs adjudication from the user. The possible unresolvable errors are InvalidTestModePage when a test mode ballot is seen when scanning in live mode or vice versa, InvalidElectionHashPage when a sheet for the wrong election is seen, InvalidPrecinctPage when a sheet for an invalid precinct is seen, UninterpretedHmpbPage for a HMPB ballot that could not be read properly, UnreadablePage for a sheet that is unrecognizable as either a HMPB or BMD ballot, and BlankPage for a blank sheet. Warnings that the user can choose to tabulate with a ballot include MarginalMark, Overvote, Undervote, and BlankBallot (a ballot where there are no votes for any contest).
Machines: vx-central-scan-frontend
Type: application-status
Description: Configuration information for the machine including the election, if the machine is in test mode, and mark threshold override values were reloaded from the backend service storing this information.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: application-status
Description: When the user is saving logs, indicates the success/failure of finding the expected log file on the machine.
Machines: All
Type: application-status
Description: Message from the scanning service about how it is configured while starting up.
Machines: vx-central-scan-frontend, vx-precinct-scan-frontend
Type: application-status
Description: Message from the admin service about how it is configured while starting up.
Machines: vx-admin-frontend
Type: application-action
Description: Application is initiating a new scanning batch on the fujitsu scanner.
Machines: vx-central-scan-frontend
Type: application-status
Description: A scanned image has returned while scanning from a fujitsu scanner, or an error was seen while scanning. Success or failure indicated by disposition.
Machines: vx-central-scan-frontend
Type: application-status
Description: A batch of sheets has completed scanning on the fujitsu scanner.
Machines: vx-central-scan-frontend
Type: application-status
Description: Message from the driver handling the fujitsu scanner regarding scanning progress.
Machines: vx-central-scan-frontend
Type: user-action
Description: The user has converted the log file to a CDF format for saving. Success or failure indicated by disposition.
Machines: All
Type: user-action
Description: Error seen when converting a single log to the CDF format. This log line will be skipped. Disposition of this log is always failure.
Machines: All
Type: user-action
Description: Message that a user triggered an attempt to reboot the machine and boot from an inserted USB drive.
Machines: All
Type: user-action
Description: Message that the machine has completed preparing to boot from USB. Success or failure indicated by the disposition.
Machines: All
Type: user-action
Description: User has triggered a reboot of the machine.
Machines: All
Type: application-action
Description: Precinct scanner state machine received an event.
Machines: vx-scan-service
Type: application-status
Description: Precinct scanner state machine transitioned states.
Machines: vx-scan-service