[fortinet_fortigate] Update Fortigate documentation #15825
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🚀 Benchmarks reportTo see the full report comment with |
andrewkroh
added
documentation
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
qcorporation
reviewed
Nov 4, 2025
| ## Note | ||
| This integration is compatible with Elastic Stack version 8.11.0 or higher. | ||
|
|
||
| ### How it works |
Contributor
Author
There was a problem hiding this comment.
No, we didn't use title case in the template or the Palo Alto documentation
qcorporation
approved these changes
Nov 4, 2025
Contributor
qcorporation
left a comment
qcorporation
left a comment
There was a problem hiding this comment.
Overall - this is really good. A major step above the existing documentation! Bravo
💚 Build Succeeded
History
cc @mjwolf |
|
Package fortinet_fortigate - 1.36.2 containing this change is available at https://epr.elastic.co/package/fortinet_fortigate/1.36.2/ |
tehbooom
pushed a commit
to tehbooom/integrations
that referenced
this pull request
Nov 19, 2025
Update documentation for the fortinet_fortigate integration. The documentation now more complete, with expanded information on supported use-cases and data types that can be collected, more details on how to completely configure the integration, and more troubleshooting information. This also includes a new packages/fortinet_fortigate/docs/knowledge_base/service_info.md file, which will be included in the built package, and can be used by other tools which use information from the package, such as LLM tools.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Update documentation for the fortinet_fortigate integration. The documentation now more complete, with expanded information on supported use-cases and data types that can be collected, more details on how to completely configure the integration, and more troubleshooting information.
This also includes a new
packages/fortinet_fortigate/docs/knowledge_base/service_info.mdfile, which will be included in the built package, and can be used by other tools which use information from the package, such as LLM tools.Checklist
changelog.ymlfile.- [ ] I have verified that any added dashboard complies with Kibana's Dashboard good practicesScreenshots
Screenshot of the updated documentation as rendered in Kibana:
