Skip to content

[Watchguard Firebox] update documentation ( LLM Generated )#17354

Open
qcorporation wants to merge 7 commits intomainfrom
470-watchguard_firebox-docs
Open

[Watchguard Firebox] update documentation ( LLM Generated )#17354
qcorporation wants to merge 7 commits intomainfrom
470-watchguard_firebox-docs

Conversation

@qcorporation
Copy link
Contributor

Proposed commit message

This PR updates the Watchguard Firebox integration documentation with improved, AI-generated content that has been manually reviewed and verified against official Watchguard Firebox documentation.

What changed:

New documentation added:

  • Add docs/knowledge_base/service_info.md with setup instructions, troubleshooting, and vendor resources
  • Fix README vendor setup steps to match official WatchGuard documentation
  • Add 9.x stack support clarification to compatibility sections
  • Consolidate duplicate vendor resources sections
  • Fix Vale linting

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 (N/A - no dashboard changes)

Author's Checklist

  • Documentation verified against official Watchguard Firebox documentation
  • Vale linting issues resolved
  • Setup steps match official Syslog configuration guide
  • Licensing information verified (standard syslog is built-in feature)

Related issues

@qcorporation qcorporation self-assigned this Feb 10, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 10, 2026

Vale Linting Results

Summary: 10 warnings, 2 suggestions found

⚠️ Warnings (10)
File Line Rule Message
packages/watchguard_firebox/_dev/build/docs/README.md 68 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/watchguard_firebox/_dev/build/docs/README.md 85 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/watchguard_firebox/docs/README.md 68 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/watchguard_firebox/docs/README.md 85 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/watchguard_firebox/docs/README.md 198 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/watchguard_firebox/docs/knowledge_base/service_info.md 51 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/watchguard_firebox/docs/knowledge_base/service_info.md 65 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/watchguard_firebox/docs/knowledge_base/service_info.md 87 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/watchguard_firebox/docs/knowledge_base/service_info.md 115 Elastic.DontUse Don't use 'and/or'.
packages/watchguard_firebox/docs/knowledge_base/service_info.md 134 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
💡 Suggestions (2)
File Line Rule Message
packages/watchguard_firebox/_dev/build/docs/README.md 173 Elastic.Versions Use 'and earlier' instead of 'and lower' when referring to versions.
packages/watchguard_firebox/docs/README.md 173 Elastic.Versions Use 'and earlier' instead of 'and lower' when referring to versions.

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.

@qcorporation qcorporation added Integration:watchguard_firebox WatchGuard Firebox documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. labels Feb 10, 2026
@qcorporation qcorporation marked this pull request as ready for review February 10, 2026 18:31
@qcorporation qcorporation requested a review from a team as a code owner February 10, 2026 18:31
@elastic-vault-github-plugin-prod

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@mjwolf mjwolf added enhancement New feature or request Team:Integration-Experience Security Integrations Integration Experience [elastic/integration-experience] labels Feb 10, 2026
@elasticmachine
Copy link

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

@elasticmachine
Copy link

💚 Build Succeeded

History

cc @qcorporation

The WatchGuard Firebox integration for Elastic enables you to collect and analyze logs from your WatchGuard Firebox appliances. By ingesting these logs into the Elastic Stack, you gain centralized visibility into your network security posture, traffic patterns, and system health. This integration helps you monitor firewall activity, detect potential security threats, and maintain an audit trail for compliance requirements.

**Log** is used to retrieve log messages generated by Firebox. See more details in the documentation [here](https://www.watchguard.com/help/docs/fireware/12/en-US/log_catalog/12_10_Log-Catalog.pdf).
This integration facilitates:
Copy link
Contributor

Choose a reason for hiding this comment

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

These points can be removed, they're duplicated in the suggested use case section

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. enhancement New feature or request 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.

3 participants