everpure/flashblade

VendorEverpure, Inc.Parsers✓
AuthorEverpureDashboards✗
Version1.2.1Alerts✗
Minimum LogScale Version1.145.0Actions✗
Use Cases

ITOps

SecOps

Scheduled Searches✗
Supported Log Formats

  • JSON

  • Syslog

    • BSD Syslog RFC 3164

  
Security DomainData Security  
Supported Timestamp Formats
FieldFormatTimezone
Vendor.syslog.timestampMMM [ ]d HH:mm:ssUTC

Everpure FlashBlade package provides parsing and normalization for Everpure FlashBlade logs, converting system events, alerts, audit logs, file operations, and session activities into a structured format.

This package processes alerts, audit events, test messages, file audit logs, GUI session logs, CLI session logs, and heartbeat messages from Pure Storage FlashBlade devices.

The parser normalizes data to a common schema based on CrowdStrike Parsing Standard (CPS) 1.0. This schema allows you to search the data without knowing the data specifically, and just knowing the common schema instead. It also allows you to combine the data more easily with other data sources which conform to the same schema.

Installing the Package in LogScale

Find the repository where you want to send the events, or Creating a Repository or View.

  1. Navigate to your repository in the LogScale interface, click Settings and then Packages on the left.

  2. Click Marketplace and install the LogScale package for (i.e. everpure/flashblade).

  3. When the package has finished installing, click Ingest tokens on the left still under the Settings.

  4. In the right panel, click + Add Token to create a new token. Give the token an appropriate name, and leave the parser unassigned, assign the parser purestorage-flashblade to the LogScale Collector Configuration as described in the documentation Configuration Examples.

    Before leaving this page, view the ingest token and copy it to your clipboard — to save it temporarily elsewhere.

    Now that you have a repository set up in LogScale along with an ingest token you are ready to send logs to LogScale.

Configurations and Sending the Logs to LogScale

You need to configure remote syslog forwarding in FlashBlade. To configure syslog forwarding:

  1. Log in to the FlashBlade console.

  2. Go to Settings > System and select the Monitoring tab.

  3. In the Syslog Servers section, click Add to add a configuration.

  4. Configure the Syslog Server Connections:

    • Name: Enter a descriptive name for the connection.

    • URI: Enter the URI string and replace the placeholders with your Falcon LogScale Collector details. Your complete URI string should look like this: udp://10.10.10.10:514

      Use the following format: 

      udp://IP-address:port

      Where udp is the transport protocol, IP-address is the IP address of the Falcon LogScale Collector, and port is the listening port for the Falcon LogScale Collector. The default port is 514.

  5. Save the configuration.

  6. Click Test to verify the connection. Ensure the test completes successfully.

Next, configure the Falcon LogScale Collector to ship the logs from your syslog server into LogScale. Follow Log Collector Install Falcon LogScale Collector and Configure Falcon LogScale Collector. Log Collector documentation also provides an example of how you can configure your syslog datasource, see Configuration Examples.

Verify Data is Arriving in LogScale

Once you have completed the above steps the data should be arriving in your LogScale repository.

Package Contents Explained

This package parses incoming data, and normalizing the data as part of that parsing. The parser normalizes the data to CrowdStrike Parsing Standard (CPS) 1.0 schema based on OpenTelemetry standards, while still preserving the original data.

If you want to search using the original field names and values, you can access those in the fields whose names are prefixed with the word Vendor. Fields which are not prefixed with Vendor are standard fields which are either based on the schema (for example, source.ip) or on LogScale conventions (@rawstring).

The fields which the parser currently maps the data to, are chosen based on what seems the most relevant, and will potentially be expanded in the future. But the parser won't necessarily normalize every field that has potential to be normalized.