Collect Pure Storage logs

Supported in:

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

Pure Storage provides all-flash enterprise storage arrays that generate audit, performance, and system event logs. The FlashArray and FlashBlade platforms support native syslog forwarding of system events, audit trails, and operational alerts. Pure Storage arrays can be configured to forward syslog using the Purity GUI, CLI, or REST API.

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 Pure Storage FlashArray
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
  • Privileged access to the Pure Storage FlashArray or FlashBlade management interface

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.

  4. 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 the Bindplane agent installation guide.

Configure the Bindplane agent to ingest syslog and send to Google SecOps

Locate the configuration file

  • Linux:

    sudo nano /opt/observiq-otel-collector/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/pure_storage:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: PURE_STORAGE
        raw_log_field: body
        ingestion_labels:
            env: production

service:
    pipelines:
        logs/pure_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/pure_storage

Configuration parameters

Replace the following placeholders:

  • Receiver configuration:

    • udplog: The receiver type based on protocol:
      • udplog for UDP syslog
      • tcplog for TCP syslog
    • 0.0.0.0: IP address to listen on:
      • 0.0.0.0 to listen on all interfaces (recommended)
      • Specific IP address to listen on one interface
    • 514: Port number to listen on (for example, 514, 1514, 6514)

  • Exporter configuration:

    • pure_storage: Descriptive name for the exporter
    • 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 from the previous step
    • 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
    • PURE_STORAGE: Log type exactly as it appears in Chronicle
    • ingestion_labels: Optional labels in YAML format (for example, env: production)

  • Pipeline configuration:

    • pure_to_chronicle: Descriptive name for the pipeline

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 Pure Storage syslog forwarding

Pure Storage FlashArray and FlashBlade arrays support native syslog forwarding. You can configure the array to send audit and system event logs to the Bindplane agent using the GUI, CLI, or REST API.

Option 1: Configure syslog using the Purity GUI

  1. Sign in to the Pure Storage FlashArray management interface.
  2. Navigate to Settings > System > Syslog Servers.
  3. Click Add (or the + icon) to add a new syslog target.
  4. In the Server field, enter the IP address of the Bindplane agent host.
  5. In the Port field, enter the port matching the Bindplane agent receiver configuration (default is UDP 514).
  6. Click Save.

Option 2: Configure syslog using the Purity CLI

  1. Connect to the FlashArray via SSH.

  2. Set the syslog server to the Bindplane agent host:

    purearray setattr --syslogserver <bindplane_agent_ip>

  3. Verify the configuration:

    purearray list --syslogserver

Option 3: Configure syslog using the REST API

  • Use the Pure Storage REST API (v2) to configure a syslog server programmatically:

    curl -X POST "https://FLASHARRAY_HOST/api/2.x/syslog-servers" \
  -H "Authorization: Bearer API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"uri": "udp://<bindplane_agent_ip>:514", "name": "chronicle-syslog"}'

UDM mapping table

Log Field UDM Mapping Logic
message_id, payload.effective_used, payload.total_extents, payload.legacy_effective_used, payload.legacy_total_extents, payload.data_reduction, payload.product, payload.array_id,signature, Method ,array_name, Controller, Interface, Module additional.fields Additional vendor-specific metadata
Description metadata.description Description of the event
timestamp metadata.event_timestamp Timestamp when the event occurred
metadata.event_type Type of event
Action metadata.product_event_type Product-specific event type
payload.version metadata.product_version Version of the product that generated the event
Sublocation network.http.parsed_user_agent Parsed user agent information
Sublocation network.http.user_agent User agent string from HTTP request
Session network.session_id Identifier for the network session
host_name principal.asset.hostname Hostname of the asset associated with the principal
Location principal.asset.ip IP address of the asset associated with the principal
host_name principal.hostname Hostname associated with the principal
Location principal.ip IP address of the principal
User principal.user.userid User ID of the principal
Result security_result.summary Summary of the security result or action
metadata.product_name Name of the product that generated the event
metadata.vendor_name Name of the vendor that generated the event

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