In this section:
The Bridge workbook (Bridge.twbx) visualizes the logs written by Tableau Bridge clients (TabBridgeClientWorker.log, TabBridgeClient.log and TabBridgeCliJob.log). It helps you quickly understand the overall health of one or more Bridge clients: which refresh and live query jobs ran, how long they took, how the client was configured, and whether the client stayed connected to the server.
TabBridgeClientWorker logs and can contain several protocol queries, each with a unique request ID.Bridge logs do not have a standard archive layout like Tableau Server logs, so LogShark only extracts nested archives whose name contains Bridge. The following layouts are supported:
LogArchive.zip → Bridge logs1.zip → Host1 → TabBridgeClientWorker.log, TabBridgeClient.log, TabBridgeCliJob.logLogArchive.zip → Bridge logs1.tar → Host1 → TabBridgeClientWorker.log, TabBridgeClient.log, TabBridgeCliJob.logLogArchive.tar → Bridge logs1.tar → Host1 → TabBridgeClientWorker.log, TabBridgeClient.log, TabBridgeCliJob.logIn each case, add one nested archive per Bridge host (for example Bridge logs1 and Bridge logs2 for Host1 and Host2).
Unexpected layouts:
LogArchive.zip → Host1.zip → TabBridgeClientWorker.log), it is not extracted.LogArchive.zip → Bridge logs1.zip → Logs → TabBridge*.log), they are processed, but the host name is shown as Logs. This makes it hard to tell hosts apart when the logset contains more than one.Logshark.exe <logsetpath> --plugins "Bridge"
This dashboard shows the jobs processed by the Bridge clients in the logset.

Views:
Filters:
Use Cases:
This dashboard shows the configuration of the Bridge client on every host in the logset, with one row per config key and one column per worker. It is the same configuration described in Change the computer or site that Bridge syncs with.

Use Cases:
This dashboard is only populated for Tableau Bridge 2026.1 and later, because the log line it relies on was added in that version.
It is based on the SelfReportingStatusUpdate log line, which the client writes every 5 seconds to report to the server that it is alive. If this line is missing for more than 5 seconds, the client could not communicate with the server and should open a new websocket to reconnect.

Views:
Filters:
Use Cases:
This dashboard shows the live queries run by the Bridge client. It is built from the TabBridgeClientWorker logs and the live query metrics logs. A protocol query usually starts within its live query, but it can end long after the live query itself ended.

Views:
create.xml, metadata.xml or prepare.xml).Filters:
How the views connect:

Use Cases:
The data is collected per Job ID. Once a Job ID is found, the following lines are scanned for status updates until RefreshCompleted is reached. FirstSeen and LastSeen are updated every time the Job ID is encountered.
TabBridgeClientWorker logs)| Field | Notes |
|---|---|
| JobID | The LUID from lines containing jobID:, stored without braces or quotes. |
| FirstSeen | Timestamp when the Job ID is first encountered in the file. |
| LastSeen | Timestamp when the Job ID is last encountered. |
| JobStartTime | Timestamp of the line with message-type: response-status and state: RefreshStarted. |
| JobEndTime | Timestamp of the line with message-type: response-status and state: RefreshCompleted. |
| AddingJobToQueueTime | Timestamp of the line with Adding remote job request to queue. |
| AddedJobToQueueTime | Timestamp of the line with Added remote job request to queue. |
| DispatchingJobTime | Timestamp of the line with Dispatching remote job request. |
| CLIProcessLaunchTime | Timestamp of the line with Launching the CLI process. |
| DataSourceUri | The value after data-source-uri, when present. |
| ErrorType | The numeric value from msg: SendStatus lines. The last available value is kept. |
| State | The result of the job. |
| RefreshType | The value from lines containing refresh-type (usually full). |
| TokenID | The LUID from lines containing Assigning token. |
| RetryCount | The numeric value from lines containing retryCount. |
| ProcessId | The numeric value from lines containing PID=. |
| HostName | The name of the folder containing the files. If the folder is called Logs, the host name is shown as Logs. |
TabBridgeCliJob logs)| Field | Notes |
|---|---|
| CPUName | CPU details. |
| Domain | Domain name of the machine running the Bridge client. |
| JobID | Job ID used for the CLI job. |
| Hostname | Host name of the machine. |
| OS | Operating system of the machine. |
| ProcessId | Process ID of the CLI job. |
| StartTime | Start time of the CLI job. |
| Tableau Version | Tableau Bridge version installed. |
| Username | User running the Bridge client. Can be a service account. |