Skip to content

[Watchguard]: Pipeline failure on traffic logs#17908

Open
qcorporation wants to merge 3 commits intomainfrom
17863-watchguard
Open

[Watchguard]: Pipeline failure on traffic logs#17908
qcorporation wants to merge 3 commits intomainfrom
17863-watchguard

Conversation

@qcorporation
Copy link
Contributor

Summary

Fixes ingest pipeline failures on ESP traffic logs where community_id ran with missing or zero ports (Painless treats null != 0 as true).

Changes

pipeline_traffic.yml: Tighten the community_id processor if so it only runs when source/destination IP and ports are present and ports are non-zero.
fields.yml: Add watchguard_firebox.log.geo_src (keyword) so pipeline output from KV-parsed geo_src="..." passes field validation.

Tests

Append an ESP traffic sample to test-traffic.log; regenerate test-traffic.log-expected.json with elastic-package test pipeline --generate.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Related issues

@qcorporation qcorporation self-assigned this Mar 19, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Mar 19, 2026

✅ Vale Linting Results

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@andrewkroh andrewkroh added documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. Integration:watchguard_firebox WatchGuard Firebox labels Mar 19, 2026
@elastic-vault-github-plugin-prod

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@qcorporation qcorporation marked this pull request as ready for review March 19, 2026 16:34
@qcorporation qcorporation requested a review from a team as a code owner March 19, 2026 16:34
@elasticmachine
Copy link

💚 Build Succeeded

History

cc @qcorporation

@andrewkroh andrewkroh added the Team:Integration-Experience Security Integrations Integration Experience [elastic/integration-experience] label Mar 19, 2026
@elasticmachine
Copy link

Pinging @elastic/integration-experience (Team:Integration-Experience)

Comment on lines +1150 to +1154
&& ctx.watchguard_firebox?.log?.destination_ip != null
&& ctx.watchguard_firebox?.log?.source_port != null
&& ctx.watchguard_firebox.log.source_port != 0
&& ctx.watchguard_firebox?.log?.destination_port != null
&& ctx.watchguard_firebox.log.destination_port != 0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remaining ? are probably redundant and can be removed.

Also, it's odd to me that we are running it against the vendor fields and not the ECS fields...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. Integration:watchguard_firebox WatchGuard Firebox Team:Integration-Experience Security Integrations Integration Experience [elastic/integration-experience]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Watchguard]: Pipeline failure on traffic logs

4 participants