找出 config.yaml 檔案。通常位於 Linux 的 /etc/bindplane-agent/ 目錄，或 Windows 的安裝目錄。
使用文字編輯器 (例如 nano、vi 或記事本) 開啟檔案。
按照下列方式編輯 config.yaml 檔案：
receivers:udplog:# Replace the port and IP address as requiredlisten_address:"0.0.0.0:514"exporters:chronicle/chronicle_w_labels:compression:gzip# Adjust the path to the credentials file you downloaded in Step 1creds_file_path:'/path/to/ingestion-authentication-file.json'# Replace with your actual customer ID from Step 2customer_id:<customer_id>
endpoint:malachiteingestion-pa.googleapis.com# Add optional ingestion labels for better organizationlog_type:'F5_DNS'raw_log_field:bodyingestion_labels:service:pipelines:logs/source0__chronicle_w_labels-0:receivers:-udplogexporters:-chronicle/chronicle_w_labels
視基礎架構需求，替換通訊埠和 IP 位址。
將 <customer_id> 替換為實際的客戶 ID。
將 /path/to/ingestion-authentication-file.json 更新為您在「取得 Google SecOps 擷取驗證檔案」部分儲存驗證檔案的路徑。
重新啟動 Bindplane 代理程式，以套用變更
如要在 Linux 中重新啟動 Bindplane 代理程式，請執行下列指令：
sudosystemctlrestartbindplane-agent
如要在 Windows 中重新啟動 Bindplane 代理程式，可以使用「服務」控制台，也可以輸入下列指令：
net stop BindPlaneAgent && net start BindPlaneAgent
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-10 (世界標準時間)。"],[],[],null,["# Collect F5 DNS logs\n===================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n| **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).\n\nThis document explains how to ingest F5 DNS logs to Google Security Operations using\nBindplane. The parser extracts fields from F5 DNS syslog messages using grok\npatterns based on the application field, then maps them to the Unified Data Model\n(UDM). It handles various F5 applications like `gtmd`, `mcpd`, `big3d`, and\nothers, parsing specific fields and setting the appropriate UDM event type,\nseverity, and descriptions based on the log level and application.\n\nBefore you begin\n----------------\n\nMake sure you have the following prerequisites:\n\n- A Google SecOps instance\n- A Windows 2016 or later, or a Linux host with `systemd`\n- If running behind a proxy, firewall [ports](/chronicle/docs/ingestion/use-bindplane-agent#verify_the_firewall_configuration) are open\n- Privileged access to F5 BIG-IP\n\nGet Google SecOps ingestion authentication file\n-----------------------------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Collection Agents**.\n3. Download the **Ingestion Authentication File**. Save the file securely on the system where Bindplane will be installed.\n\nGet Google SecOps customer ID\n-----------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Profile**.\n3. Copy and save the **Customer ID** from the **Organization Details** section.\n\nInstall the Bindplane agent\n---------------------------\n\nInstall the Bindplane agent on your Windows or Linux operating system according\nto the following instructions.\n\n### Windows installation\n\n1. Open the **Command Prompt** or **PowerShell** as an administrator.\n2. Run the following command:\n\n msiexec /i \"https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi\" /quiet\n\n### Linux installation\n\n1. Open a terminal with root or sudo privileges.\n2. Run the following command:\n\n sudo sh -c \"$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)\" install_unix.sh\n\n### Additional installation resources\n\nFor additional installation options, consult the\n[installation guide](/chronicle/docs/ingestion/use-bindplane-agent#install_the_bindplane_agent).\n\nConfigure the Bindplane agent to ingest Syslog and send to Google SecOps\n------------------------------------------------------------------------\n\n1. Access the configuration file:\n - Locate the `config.yaml` file. Typically, it's in the `/etc/bindplane-agent/` directory on Linux or in the installation directory on Windows.\n - Open the file using a text editor (for example, `nano`, `vi`, or Notepad).\n2. Edit the `config.yaml` file as follows:\n\n receivers:\n udplog:\n # Replace the port and IP address as required\n listen_address: \"0.0.0.0:514\"\n\n exporters:\n chronicle/chronicle_w_labels:\n compression: gzip\n # Adjust the path to the credentials file you downloaded in Step 1\n creds_file_path: '/path/to/ingestion-authentication-file.json'\n # Replace with your actual customer ID from Step 2\n customer_id: \u003ccustomer_id\u003e\n endpoint: malachiteingestion-pa.googleapis.com\n # Add optional ingestion labels for better organization\n log_type: 'F5_DNS'\n raw_log_field: body\n ingestion_labels:\n\n service:\n pipelines:\n logs/source0__chronicle_w_labels-0:\n receivers:\n - udplog\n exporters:\n - chronicle/chronicle_w_labels\n\n - Replace the port and IP address as required in your infrastructure.\n - Replace `\u003ccustomer_id\u003e` with the actual customer ID.\n - Update `/path/to/ingestion-authentication-file.json` to the path where the authentication file was saved in the [Get Google SecOps ingestion authentication file](/chronicle/docs/ingestion/default-parsers/F5-dns#get-auth-file) section.\n\nRestart the Bindplane agent to apply the changes\n------------------------------------------------\n\n- To restart the Bindplane agent in **Linux**, run the following command:\n\n sudo systemctl restart bindplane-agent\n\n- To restart the Bindplane agent in **Windows** , you can either use the **Services**\n console or enter the following command:\n\n net stop BindPlaneAgent && net start BindPlaneAgent\n\nConfigure a pool of remote logging servers\n------------------------------------------\n\n1. Sign in to the **F5 BIG-IP** web UI.\n2. On the **Main** tab, go to **DNS \\\u003e Delivery \\\u003e Load Balancing \\\u003e Pools or Local Traffic \\\u003e Pools**.\n3. Click **Create**.\n4. Provide the following configuration details:\n - **Name**: Enter a unique name for the pool.\n - Using **New Members** setting:\n - Enter the Bindplane agent IP address in the **Address** field.\n - Enter the Bindplane agent port number in the **Service Port** field.\n5. Click **Add \\\u003e Finished**.\n\nConfigure the remote log destination\n------------------------------------\n\n1. On the **Main** tab, go to **System \\\u003e Logs \\\u003e Configuration \\\u003e Log Destinations**.\n2. Click **Create**.\n3. Provide the following configuration details:\n - **Name**: Enter a unique name for this destination.\n - **Type** : Select **Remote High-Speed Log**.\n - **Pool Name**: Select the pool of remote log servers to which you want the BIG-IP system to send log messages.\n - **Protocol**: Select the protocol used.\n4. Click **Finished**.\n\nCreating a formatted remote log destination\n-------------------------------------------\n\n1. On the **Main** tab, go to **System \\\u003e Logs \\\u003e Configuration \\\u003e Log Destinations**.\n2. Click **Create**.\n3. Provide the following configuration details:\n - **Name**: Enter a unique name for this destination.\n - **Type** : Select **Remote Syslog**.\n - **Format**: Select the log format.\n - **Forward To** : Select **High-Speed Log Destination \\\u003e the destination that points to the pool of remote Syslog servers**.\n4. Click **Finished**.\n\nConfigure Log Publisher\n-----------------------\n\n1. On the **Main** tab, go to **System \\\u003e Logs \\\u003e Configuration \\\u003e Log Publishers**.\n2. Click **Create**.\n3. Provide the following configuration details:\n - **Name**: Enter a unique name for this publisher.\n - **Destinations** : Select the newly-created destination for **Remote Syslog** from the **Available** list, and then click keyboard_double_arrow_left **Move** to move the destination to the **Selected** list.\n4. Click **Finished**.\n\nConfigure a custom DNS logging profile\n--------------------------------------\n\n1. On the **Main** tab, go to **DNS \\\u003e Delivery \\\u003e Profiles \\\u003e Other \\\u003e DNS Logging or Local Traffic \\\u003e Profiles \\\u003e Other \\\u003e DNS Logging**.\n2. Click **Create**.\n3. Provide the following configuration details:\n - **Name**: Enter a unique name for this profile.\n - **Log Publisher**: Select the newly-created destination to which the system sends DNS log entries.\n - **Log Queries** : Select the **Enabled** checkbox.\n - **Log Responses** : Select the **Enabled** checkbox.\n - **Include Query ID** : Select the **Enabled** checkbox.\n4. Click **Finished**.\n\nAdd the DNS profile to the DNS Listener\n---------------------------------------\n\n1. On the **Main** tab, go to **DNS \\\u003e Delivery \\\u003e Listeners \\\u003e select DNS listener**.\n2. From the **DNS profile** in the **Service** section, select the **DNS profile** that you configured previously.\n3. Click **Update**.\n\nUDM mapping table\n-----------------\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
