Console
    Start free

    Collect HPE iLO logs

    Supported in:

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

    HPE iLO (Integrated Lights-Out) is a remote server management processor that generates syslog messages for hardware events, authentication attempts, DNS queries, and system status changes. The parser uses JSON and grok pattern matching to extract fields from HP iLO log formats 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 HPE iLO management interface
    • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
    • Privileged access to HPE iLO

    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 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 IDfrom the Organization Detailssection.

    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 Promptor PowerShellas 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  
/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/hpe_ilo 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 '/etc/bindplane-agent/ingestion-auth.json' 
  
 customer_id 
 : 
  
 '<customer_id>' 
  
 endpoint 
 : 
  
 malachiteingestion-pa.googleapis.com 
  
 log_type 
 : 
  
 HPE_ILO 
  
 raw_log_field 
 : 
  
 body 
 service 
 : 
  
 pipelines 
 : 
  
 logs/hpe_ilo_to_chronicle 
 : 
  
 receivers 
 : 
  
 - 
  
 udplog 
  
 exporters 
 : 
  
 - 
  
 chronicle/hpe_ilo

    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 syslog in HPE iLO

    1. Sign in to the HPE iLOweb UI.
    2. Go to Management > Remote Syslogtab.
    3. Click EnableiLO Remote Syslog.
    4. Provide the following configuration details:
      • Remote Syslog Port: Enter the Bindplane port number (for example, 514 ).
      • Remote Syslog Server: Enter the Bindplane IP address.
    5. Click Send Test Syslogand validate it was received.
    6. Click Apply.

    UDM mapping table

    Log field UDM mapping Logic
    data
    		This field is parsed and mapped to various UDM fields based on its content.
    data.HOSTNAME
    		principal.hostname Mapped when the first grok pattern in the "message" field matches, or when the "description" field contains "Host". Determines if event_type is STATUS_UPDATE.
    data.HOSTNAME
    		network.dns.questions.name Populated by grok pattern matching "DATA" in "message". Used to populate dns.questions if not empty and doesn't contain "(?i)not found".
    data.HOSTNAME
    		target.user.user_display_name Populated by grok pattern matching "DATA" in "message".
    data.IP
    		target.ip Populated by grok patterns matching "IP" in "message" or "summary".
    data.WORD
    		metadata.product_event_type Populated by grok pattern matching "WORD" in "message".
    data.GREEDYDATA
    		security_result.summary Populated by grok pattern matching "GREEDYDATA" in "message". Used to determine network.application_protocol and event_type based on its content.
    data.TIMESTAMP_ISO8601
    		metadata.event_timestamp Populated by the date plugin based on various timestamp formats.
    data.MONTHNUM
    		Not Mapped
    data.MONTHDAY
    		Not Mapped
    data.YEAR
    		Not Mapped
    data.TIME
    		Not Mapped
    data.HOST
    		principal.hostname Mapped when the second grok pattern in the "message" field matches.
    data.INT
    		Not Mapped
    data.UserAgent
    		network.http.user_agent Mapped when the description field contains User-Agent .
    data.Connection
    		security_result.description Mapped when the description field contains Connection .
    N/A
    		 metadata.event_type Defaults to GENERIC_EVENT . Changes to STATUS_UPDATE if data.HOSTNAME is successfully mapped to principal.hostname, NETWORK_DNS if question is populated, or USER_LOGIN if summary contains Browser login .
    N/A
    		 metadata.vendor_name Hardcoded to HP .
    N/A
    		 metadata.log_type Set to HPE_ILO .
    N/A
    		 network.application_protocol Set to LDAP if summary contains LDAP , or DNS if question is populated.
    N/A
    		 extensions.auth.type Set to MACHINE if summary contains Browser login .

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

    Create a Mobile Website
    View Site in Mobile | Classic
    Share by: