Collect Tableau logs
This document explains how to ingest Tableau logs to Google Security Operations using Bindplane.
Tableau is a business intelligence and data visualization platform that generates user activity, authentication, and audit logs. Tableau Server stores log files on the server file system, making file-based collection ideal for ingestion.
Before you begin
Make sure you have the following prerequisites:
- A Google SecOps instance
- Windows Server 2016 or later, or Linux host with
systemd - Network connectivity between the Bindplane agent and the Tableau Server host
- If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
- Privileged access to Tableau Server with administrator permissions
- Access to Tableau Server log files on the server file system
Get Google SecOps ingestion authentication file
- Sign in to the Google SecOps console.
- Go to SIEM Settings > Collection Agents.
Download the Ingestion Authentication File. Save the file securely on the system where Bindplane will be installed.
Get Google SecOps customer ID
- Sign in to the Google SecOps console.
- Go to SIEM Settings > Profile.
Copy and save the Customer ID from the Organization Details section.
Install the Bindplane agent
Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.
Windows installation
- Open Command Prompt or PowerShell as an administrator.
Run the following command:
msiexec /i "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" /quietWait for the installation to complete.
Verify the installation by running:
sc query observiq-otel-collector
The service should show as RUNNING.
Linux installation
- Open a terminal with root or sudo privileges.
Run the following command:
sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)" install_unix.shWait for the installation to complete.
Verify the installation by running:
sudo systemctl status observiq-otel-collector
The service should show as active (running).
Additional installation resources
For additional installation options and troubleshooting, see Bindplane agent installation guide.
Configure Bindplane agent to ingest syslog and send to Google SecOps
Locate the configuration file
Linux:
sudo nano /etc/bindplane-agent/config.yamlWindows:
notepad "C:\Program Files\observIQ OpenTelemetry Collector\config.yaml"
Edit the configuration file
Replace the entire contents of
config.yamlwith the following configuration:receivers: filelog: include: - /var/opt/tableau/tableau_server/data/tabsvc/logs/httpd/access.*.log - /var/opt/tableau/tableau_server/data/tabsvc/logs/vizqlserver/*.log - /var/opt/tableau/tableau_server/data/tabsvc/logs/backgrounder/*.log start_at: beginning exporters: chronicle/tableau: compression: gzip creds_file_path: '/etc/bindplane-agent/ingestion-auth.json' customer_id: '<customer_id>' endpoint: malachiteingestion-pa.googleapis.com log_type: TABLEAU raw_log_field: body ingestion_labels: env: production service: pipelines: logs/tableau_to_chronicle: receivers: - filelog exporters: - chronicle/tableau
Configuration parameters
Replace the following placeholders:
Receiver configuration:
filelog: The receiver type for collecting log files from diskinclude: List of file paths or glob patterns to monitor:- Linux:
/var/opt/tableau/tableau_server/data/tabsvc/logs/ - Windows:
C:\ProgramData\Tableau\Tableau Server\data\tabsvc\logs\ - Key log files include
httpd/access.*.log(Apache access logs),vizqlserver/*.log(VizQL server logs), andbackgrounder/*.log(background task logs) - Adjust the paths to match your Tableau Server installation
- Linux:
start_at: Set tobeginningto read existing log files from the start, orendto only read new entries
Exporter configuration:
tableau: Descriptive name for the exportercreds_file_path: Full path to ingestion authentication file:- Linux:
/etc/bindplane-agent/ingestion-auth.json - Windows:
C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
- Linux:
<customer_id>: Customer ID from the previous stependpoint: Regional endpoint URL:- US:
malachiteingestion-pa.googleapis.com - Europe:
europe-malachiteingestion-pa.googleapis.com - Asia:
asia-southeast1-malachiteingestion-pa.googleapis.com - See Regional Endpoints for complete list
- US:
TABLEAU: Log type exactly as it appears in Chronicleingestion_labels: Optional labels in YAML format (for example,env: production)
Pipeline configuration:
* tableau_to_chronicle: Descriptive name for the pipeline
Save the configuration file
- After editing, save the file:
- Linux: Press
Ctrl+O, thenEnter, thenCtrl+X - Windows: Click File > Save
- Linux: Press
Restart the Bindplane agent to apply the changes
To restart the Bindplane agent in Linux:
Run the following command:
sudo systemctl restart observiq-otel-collectorVerify the service is running:
sudo systemctl status observiq-otel-collectorCheck logs for errors:
sudo journalctl -u observiq-otel-collector -f
To restart the Bindplane agent in Windows:
Choose one of the following options:
- Command Prompt or PowerShell as administrator:
net stop observiq-otel-collector && net start observiq-otel-collector- Services console:
- Press
Win+R, typeservices.msc, and press Enter. - Locate observIQ OpenTelemetry Collector.
- Right-click and select Restart.
- Press
Verify the service is running:
sc query observiq-otel-collectorCheck logs for errors:
type "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log"
Verify Tableau Server log file locations
- Sign in to the Tableau Server host with administrator privileges.
- Verify the log file directories:
- Linux:
/var/opt/tableau/tableau_server/data/tabsvc/logs/ - Windows:
C:\ProgramData\Tableau\Tableau Server\data\tabsvc\logs\
- Linux:
- Key log subdirectories and files:
httpd/access.*.log: Apache access logs with HTTP request detailsvizqlserver/*.log: VizQL server logs with visualization query activitybackgrounder/*.log: Background task logs with scheduled job activity
(Optional) Generate a log archive using the TSM command-line tool for verification:
tsm maintenance ziplogs -a -t -o -f tableau-logs.zipUpdate the
includepaths in the Bindplane agentconfig.yamlif the log directory differs from the defaults.
UDM mapping table
| Log Field | UDM Mapping | Logic |
|---|---|---|
| dataserver_permissions, local_dataserver, saved_credentials_viewerid, locale, server_oauth, :id, server_viewerid, dataserver_version, tablename, ElapsedTime, LastStatus, Timeszone | additional.fields | Merged key-value pairs from specified fields |
| Content | metadata.description | Value copied directly after removing "_" |
| ID, RemoteHost | metadata.event_type | Set to USER_UNCATEGORIZED if ID not empty, STATUS_UPDATE if RemoteHost present, GENERIC_EVENT otherwise |
| protocol | network.application_protocol | Value copied directly |
| http_version | network.application_protocol_version | Value copied directly |
| method | network.http.method | Value copied directly after removing "" |
| SizeBytes | network.received_bytes | Converted to uinteger |
| session_id | network.session_id | Value copied directly |
| Workername | principal.asset.hostname | Value copied directly |
| RemoteHost | principal.asset.ip | Value copied directly |
| Workername | principal.hostname | Value copied directly |
| RemoteHost | principal.ip | Value copied directly |
| Port | principal.nat_port | Converted to integer |
| ID | principal.user.product_object_id | Value copied directly |
| RemoteUser | principal.user.userid | Value copied directly if not empty or "_" |
| logging_ctx | security_result.detection_fields | Merged key-value pair from logging_ctx |
| path | target.file.full_path | Value copied directly |
| dbname | target.resource.name | Value copied directly |
| metadata.product_name | Set to "Tableau" | |
| metadata.vendor_name | Set to "TABLEAU" |
Need more help? Get answers from Community members and Google SecOps professionals.