Collect Dell OpenManage logs

Parser Version: 1.0

Supported in:

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

Dell OpenManage Enterprise is a systems management console that generates syslog messages for audit events, configuration changes, and device compliance. The parser extracts key-value pairs from raw logs using grok patterns and maps them to the Unified Data Model (UDM).

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 Dell OpenManage Enterprise server
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
  • Privileged access to Dell OpenManage Enterprise

Get Google SecOps credentials for the Bindplane agent

To authenticate the Bindplane agent to Google SecOps, choose one of the following methods:

  • New deployments: Use the Chronicle API (Option 1).
  • Legacy deployments: Continue using the ingestion authentication file (Option 2) until the Ingestion API is discontinued on July 20, 2027.
  1. Sign in to the Google Cloud console and select the Google Cloud project that is linked to your Google SecOps instance.
  2. Go to IAM & Admin > Service Accounts.
  3. Click Create service account.
  4. Provide the following configuration details:
    • Service account name: Enter a name for the account (for example, bindplane-ingest).
    • Service account description: Enter a description (for example, Bindplane agent log ingestion).
  5. Click Create and continue.
  6. In the Grant this service account access to project section, click Select a role and select Chronicle Editor.
  7. Click Continue, and then click Done.
  8. Click the service account you created, and then go to the Keys tab.
  9. Click Add key > Create new key.
  10. Select JSON and click Create. The key file is downloaded to your computer.
  11. Save the key file as ingestion-auth.json in the Bindplane collector directory (/opt/observiq-otel-collector/ingestion-auth.json on Linux or C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json on Windows), or update creds_file_path in config.yaml to match the path where you save it.
  12. Go to IAM & Admin > Settings and copy the Project number. You'll need it for the exporter configuration.

Option 2: Download the ingestion authentication file (legacy)

  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 the Bindplane agent 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/dell_openmanage:
    protocol: https
    # Region of your instance, for example us, europe, asia-southeast1
    location: <LOCATION>
    # Project number of the Google Cloud project linked to the instance
    project: '<PROJECT_NUMBER>'
    compression: gzip
    creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
    customer_id: '<customer_id>'
    endpoint: chronicle.googleapis.com
    log_type: DELL_OPENMANAGE
    raw_log_field: body

service:
  pipelines:
    logs/dell_openmanage_to_chronicle:
      receivers:
        - udplog
      exporters:
        - chronicle/dell_openmanage

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 the service account JSON key file (Option 1):
      • Linux: /opt/observiq-otel-collector/ingestion-auth.json
      • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
    • customer_id: Customer ID copied from the Google SecOps console
    • location: Replace <LOCATION> with the region of your Google SecOps instance (for example, us, europe, or asia-southeast1). The exporter prefixes chronicle.googleapis.com with this value. See Regional Endpoints for the complete list.
    • project: Replace <PROJECT_NUMBER> with the project number from IAM & Admin > Settings.
    • endpoint: Keep set to chronicle.googleapis.com.

Legacy ingestion API exporter

  • If you use the ingestion authentication file from Option 2, replace the exporters block with the following. Set creds_file_path to the path to the ingestion authentication file, and if your instance is outside the US, replace malachiteingestion-pa.googleapis.com with your regional endpoint (for example, europe-malachiteingestion-pa.googleapis.com).

    exporters:
  chronicle/dell_openmanage:
    compression: gzip
    creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
    customer_id: '<customer_id>'
    endpoint: malachiteingestion-pa.googleapis.com
    log_type: DELL_OPENMANAGE
    raw_log_field: body

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 syslog for Dell OpenManage Enterprise

  1. Sign in to the Dell OpenManage Enterprise web console.
  2. Go to Application Settings > Alerts > Syslog Configuration.
  3. Enable syslog forwarding.
  4. Provide the following details:
    • Server: Enter the IP address or hostname of the Bindplane agent.
    • Port: Enter the port number (for example, 514).
  5. Click Apply.

Configure alert policies (optional)

  1. Go to Alerts > Alert Policies > Create.
  2. Provide the following configuration details:
    • In the Create Alert Policy dialog, enter a meaningful Name and Description for the policy.
    • Verify the Enable Policy checkbox is selected.
    • Click Next.
    • Category: Expand Application and select all the categories and subcategories of the appliance logs.
    • Click Next.
    • Severity: Select the All checkbox.
    • Click Next.
    • Actions: Select Syslog.
    • Click Enable and enter the Bindplane agent IP address.
    • Click Next.
  3. Click Finish.

Supported Dell OpenManage sample logs

  • SYSLOG + KV

    <156>2022-02-06T05:00:33.181319+00:00 internal-log-relay-01 EEMI Audit event from device with
{ IP } 192.168.100.100
{ HostName } workstation-prod-01
{ Severity } Warning
{ MessageID } CDEV9000
{ Message } This device and several others has become non compliant after running compliance task: Alpha.
{ Recommended Action } Update the device or component firmware using a catalog or update package.

  • SYSLOG + KV + internal fields

    <158>2022-01-15T15:59:55.576332+00:00 internal-log-relay-01 EEMI Configuration event from device with
{ IP } null
{ HostName } null
{ Severity } Info
{ MessageID } CSEC0053
{ Message } Description:Local user dummy_user deleted. User Name:admin_account Received from address:172.16.254.1
{ Recommended Action } Instrumentation didn't provide any recommended action for this event.

  • Protocol/diagnostic header

    Client-ATV-Sharing-Version**: `1.2`

UDM mapping table

Log field UDM mapping Logic
data.HostName read_only_udm.principal.hostname The value of HostName from the raw log is directly mapped to read_only_udm.principal.hostname.
data.IP read_only_udm.target.ip The value of IP from the raw log is directly mapped to read_only_udm.target.ip.
data.Message read_only_udm.metadata.description The value of Message from the raw log is directly mapped to read_only_udm.metadata.description.
data.MessageID read_only_udm.additional.fields.value.string_value The value of MessageID from the raw log is directly mapped to read_only_udm.additional.fields.value.string_value.
data.Recommended Action read_only_udm.additional.fields.value.string_value The value of Recommended Action from the raw log is directly mapped to read_only_udm.additional.fields.value.string_value.
data.Severity read_only_udm.security_result.severity The value of Severity from the raw log is mapped to read_only_udm.security_result.severity after being converted to uppercase.
data.timestamp.nanos read_only_udm.metadata.event_timestamp.nanos The value of timestamp.nanos from the raw log is directly mapped to read_only_udm.metadata.event_timestamp.nanos.
data.timestamp.seconds read_only_udm.metadata.event_timestamp.seconds The value of timestamp.seconds from the raw log is directly mapped to read_only_udm.metadata.event_timestamp.seconds.
read_only_udm.metadata.event_type This field is determined based on the content of the Message field from the raw log.
read_only_udm.metadata.log_type This field is hardcoded to DELL_OPENMANAGE in the parser code.
read_only_udm.metadata.product_name This field is hardcoded to DELL_OPENMANAGE in the parser code.
read_only_udm.metadata.vendor_name This field is hardcoded to DELL in the parser code.
read_only_udm.additional.fields.key This field name is hardcoded in the parser code. The value of this field is MessageID or Recommended_Action.
host_name event.idm.read_only_udm.intermediary.hostname Mapped from changelog

Change Log

View the Change Log for this parser

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