Invox Dictation SDK Version:

Browser Logs

Invox Dictation SDK incorporates a logging system for the Browser side.

The SDK records logs in the browser and sends session logs through the active SDK session. It does not create a log file on the client machine and does not require a local Dictation Service.

Browser storage

Before login, the SDK stores temporary records in browser Local Storage under INVOX_LOG-TEMP. After a successful login, it moves those records to INVOX_LOG-<USER_LOGIN> and associates subsequent session logs with that user.

How it works

Logging is available before and during a session. When the user logs in, the SDK initializes the session logger and sends any retained user logs. When the user logs out, it sends unsent session logs before returning to the temporary browser logger.

Logging targets

You can retain logs in Local Storage or send them through the active SDK session. At the same time you can show log messages in the browser console.

To modify the logging target, use INVOX.ChangeLogTarget().

Local Storage

INVOX Logger uses a maximum of 1 MB of memory in Local Storage.

In this mode, the Logger records all logs in the Browser Local Storage until reaching the maximum size set (1 MB). INVOX Logger sends the logs to the Server when:

  • The user starts a session (Login).
  • The user ends a session (Logout).
  • The maximum size in Local Storage is reached.

Only Server

This logger target takes precedence over the Local Storage target.

In this mode, the Logger sends each log through the active SDK session without storing it locally.

Browser Console

This target can be used at the same time as another one.

In this mode, the Logger only displays the information in the Browser Console.

Table of Contents