From 9546d9e8c63eae58847212d2ccddc074a5ed3db5 Mon Sep 17 00:00:00 2001 From: Derek Date: Mon, 16 Nov 2026 09:23:33 +1100 Subject: [PATCH] docs(filebeat): mark the bundled pipeline legacy for DFE/XDR 2.0 and 2.1 The bundled filebeat pipeline stays for compatibility with DFE/XDR 2.0 and 2.1 filebeat feeds. Its README and the header in filebeat.yaml call it legacy instead of interim, matching dfe-transform-vrl. - It supports only the Cisco IOS, Meraki and Umbrella modules. - It fetches nothing from Elastic at build, test or run time. - New feeds use dfe-transform-elastic. A move there is planned for 2.0 and 2.1 feeds. --- pipelines/filebeat/README.md | 8 +++----- pipelines/filebeat/filebeat.yaml | 9 ++++----- 2 files changed, 7 insertions(+), 10 deletions(-) diff --git a/pipelines/filebeat/README.md b/pipelines/filebeat/README.md index db221c2..7f16b7a 100644 --- a/pipelines/filebeat/README.md +++ b/pipelines/filebeat/README.md @@ -8,13 +8,11 @@ License: BUSL-1.1 Copyright: (c) 2026 HYPERI PTY LIMITED --> -# Bundled pipeline: filebeat-compat (INTERIM) +# Bundled pipeline: filebeat-compat (LEGACY) -A pre-canned transform file that keeps DFE 2.1 filebeat feeds working on dfe-transform-vector: the same VRL dfe-transform-vrl runs, wrapped in a Vector `remap` and carrying the enrichment table it needs. Point `transforms.dir` at this directory, mount the table, and the pipeline runs -- there is nothing to author. The modules, the routing rules, the departures from DFE 2.1 and the known limitations are documented once, in dfe-transform-vrl `pipelines/filebeat/README.md`, and apply here unchanged. +A pre-canned transform file that keeps DFE/XDR 2.0 and 2.1 filebeat feeds working on dfe-transform-vector: the same VRL dfe-transform-vrl runs, wrapped in a Vector `remap` and carrying the enrichment table it needs. Point `transforms.dir` at this directory, mount the table, and the pipeline runs -- there is nothing to author. The modules, the routing rules, the departures from DFE 2.1 and the known limitations are documented once, in dfe-transform-vrl `pipelines/filebeat/README.md`, and apply here unchanged. -> **INTERIM.** Elastic compatibility is being replaced by -> `dfe-transform-elastic` (Rust-native). New integrations -> should NOT build on this pipeline. +> **LEGACY.** Backwards compatibility for DFE/XDR 2.0 and 2.1 filebeat feeds, frozen at the Cisco IOS, Meraki and Umbrella modules. It takes no new modules and fetches nothing from Elastic at build, test or run time. New feeds use `dfe-transform-elastic`, and 2.0 and 2.1 feeds should plan to move there. ## Using it diff --git a/pipelines/filebeat/filebeat.yaml b/pipelines/filebeat/filebeat.yaml index 789108d..2f70f32 100644 --- a/pipelines/filebeat/filebeat.yaml +++ b/pipelines/filebeat/filebeat.yaml @@ -39,7 +39,7 @@ transforms: - dfe_source source: | ############################################################################## - # dfe-transform-vrl bundled pipeline: filebeat-compat -- INTERIM + # dfe-transform-vrl bundled pipeline: filebeat-compat -- LEGACY # # Single-file port of the DFE 2.1 Vector filebeat transform templates # (dfe-vector-templates src/core_templates 14x family): @@ -56,10 +56,9 @@ transforms: # umbrella templates differed only in the hardcoded .log.file.path seed; # they collapse to one body driven by the detected log type. # - # INTERIM: this pipeline keeps DFE 2.1 filebeat feeds working on - # dfe-transform-vrl. Elastic compatibility is being replaced by - # dfe-transform-elastic (Rust-native), and new integrations should NOT - # build on this file. + # LEGACY: backwards compatibility for DFE/XDR 2.0 and 2.1 filebeat feeds + # on dfe-transform-vrl, frozen at these three modules. New feeds use + # dfe-transform-elastic. # # Deliberate departures from the 2.1 templates: # - geoip enrichment is NOT ported: dfe-loader owns geoip enrichment in