Collect Tintri logs

Supported in:

This document explains how to ingest Tintri logs to Google Security Operations using the Bindplane agent.

Tintri is a VM-aware intelligent storage platform that generates performance, capacity, and system event logs. It provides storage management optimized for virtualized environments in on-premise data centers.

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 Tintri VMstore appliance
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
  • Privileged access to the Tintri VMstore or Tintri Global Center with administrator permissions

Get Google SecOps ingestion authentication file

  1. Sign in to the Google SecOps console.
  2. Go to SIEM Settings > Collection Agents.

  3. Download the Ingestion Authentication File. Save the file securely on the system where Bindplane will be installed.

Get Google SecOps customer ID

  1. Sign in to the Google SecOps console.
  2. Go to SIEM Settings > Profile.

  3. 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

  1. Open Command Prompt or PowerShell as an administrator.

  2. Run the following command:

    msiexec /i "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" /quiet

  3. Wait for the installation to complete.

  4. Verify the installation by running:

    sc query observiq-otel-collector

    The service should show as RUNNING.

Linux installation

  1. Open a terminal with root or sudo privileges.

  2. Run the following command:

    sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)" install_unix.sh

  3. Wait for the installation to complete.

  4. 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.yaml

  • Windows:

    notepad "C:\Program Files\observIQ OpenTelemetry Collector\config.yaml"

Edit the configuration file

  • Replace the entire contents of config.yaml with the following configuration:

    receivers:
    udplog:
        listen_address: "0.0.0.0:514"

exporters:
    chronicle/tintri:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: TINTRI
        raw_log_field: body

service:
    pipelines:
        logs/tintri_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/tintri

Configuration parameters

Replace the following placeholders:

  • Receiver configuration:

    • listen_address: IP address and port to listen on:
      • 0.0.0.0 to listen on all interfaces (recommended)
      • Port 514 is the standard syslog port (requires root on Linux; use 1514 for non-root)

  • Exporter configuration:

    • creds_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
    • customer_id: Customer ID copied from the Google SecOps console
    • endpoint: 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

Save the configuration file

  • After editing, save the file:

    • Linux: Press Ctrl+O, then Enter, then Ctrl+X
    • Windows: Click File > Save

Restart the Bindplane agent to apply the changes

  • To restart the Bindplane agent in Linux, run the following command:

    sudo systemctl restart observiq-otel-collector

    1. Verify the service is running:

      sudo systemctl status observiq-otel-collector

    2. Check 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:

      1. Press Win+R, type services.msc, and press Enter.
      2. Locate observIQ OpenTelemetry Collector.
      3. Right-click and select Restart.

      4. Verify the service is running:

        sc query observiq-otel-collector

      5. Check logs for errors:

        type "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log"

Configure Tintri syslog forwarding

  1. Sign in to the Tintri VMstore management console.
  2. Go to Settings > Notifications > Syslog.
  3. Click Add to create a new syslog server entry.
  4. Provide the following configuration details:
    • Server: Enter the IP address of the Bindplane agent host.
    • Port: Enter 514.
    • Protocol: Select UDP.
  5. Click Save or Apply to save the configuration.
  6. Verify that logs are being sent by checking the Bindplane agent logs.

UDM mapping table

Log Field UDM Mapping Logic
description extensions.auth.type Set to "MACHINE" if description matches "logged in|login" or "logged out|logout"
event_timestamp metadata.event_timestamp Converted using date match "MMM dd HH:mm:ss " to timestamp
hostname,user_id,request_path,description metadata.event_type Set to "USER_LOGIN" if hostname not empty and (user_id not empty or request_path not empty) and description matches "logged in|login"; "USER_LOGOUT" if hostname not empty and (user_id not empty or request_path not empty) and description matches "logged out|logout"; "USER_UNCATEGORIZED" if hostname not empty and (user_id not empty or request_path not empty); "STATUS_UPDATE" if hostname not empty; else "GENERIC_EVENT"
user_event metadata.product_event_type Value copied directly
log_id metadata.product_log_id Value copied directly
http_method network.http.method Value copied directly
hostname principal.asset.hostname Value copied directly
client_ip principal.asset.ip Merged from client_ip
hostname principal.hostname Value copied directly
client_ip principal.ip Merged from client_ip
id principal.process.pid Converted to string
logger principal.resource.attribute.labels Merged as label with key "logger" and value from logger
description security_result.description Value copied directly
component,thread,client_type security_result.detection_fields Merged as labels with keys "component", "thread", "client_type" and values from respective fields
log_level security_result.severity Set to "INFORMATIONAL" if log_level matches (?i)(DEBUG|INFO|AUDIT|NOTICE); "ERROR" if (?i)ERROR; "MEDIUM" if (?i)(WARNING|WARN)
status security_result.summary Value copied directly
request_path target.url Value copied directly
user_id target.user.userid Value copied directly
metadata.product_name Set to "Tintri"
metadata.vendor_name Set to "Tintri"

Need more help? Get answers from Community members and Google SecOps professionals.