[fortinet_fortiproxy] Update Fortinet FortiProxy documentation#17294
Merged
vinit-chauhan merged 7 commits intoelastic:mainfrom Feb 26, 2026
Merged
[fortinet_fortiproxy] Update Fortinet FortiProxy documentation#17294vinit-chauhan merged 7 commits intoelastic:mainfrom
vinit-chauhan merged 7 commits intoelastic:mainfrom
Conversation
Update documentation for the fortinet_fortiproxy integration. This expands the information on the use-cases supported by the integration, and the data collected. It also reformats the set up instructions to make them easier to follow, and adds common troubleshooting issues. Assisted by Google Gemini
mjwolf
added
the
documentation
mjwolf
added
enhancement
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
Contributor
Vale Linting ResultsSummary: 17 warnings, 7 suggestions found
|
| File | Line | Rule | Message |
|---|---|---|---|
| packages/fortinet_fortiproxy/_dev/build/docs/README.md | 200 | Elastic.DontUse | Don't use 'very'. |
| packages/fortinet_fortiproxy/docs/README.md | 200 | Elastic.DontUse | Don't use 'very'. |
| packages/fortinet_fortiproxy/docs/README.md | 231 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| packages/fortinet_fortiproxy/docs/README.md | 244 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| packages/fortinet_fortiproxy/docs/README.md | 266 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'. |
| packages/fortinet_fortiproxy/docs/README.md | 286 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| packages/fortinet_fortiproxy/docs/knowledge_base/service_info.md | 60 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| packages/fortinet_fortiproxy/docs/knowledge_base/service_info.md | 91 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| packages/fortinet_fortiproxy/docs/knowledge_base/service_info.md | 91 | Elastic.EndPuntuaction | Don't end headings with punctuation. |
| packages/fortinet_fortiproxy/docs/knowledge_base/service_info.md | 94 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| packages/fortinet_fortiproxy/docs/knowledge_base/service_info.md | 105 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| packages/fortinet_fortiproxy/docs/knowledge_base/service_info.md | 105 | Elastic.EndPuntuaction | Don't end headings with punctuation. |
| packages/fortinet_fortiproxy/docs/knowledge_base/service_info.md | 108 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| packages/fortinet_fortiproxy/docs/knowledge_base/service_info.md | 118 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| packages/fortinet_fortiproxy/docs/knowledge_base/service_info.md | 118 | Elastic.EndPuntuaction | Don't end headings with punctuation. |
| packages/fortinet_fortiproxy/docs/knowledge_base/service_info.md | 121 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| packages/fortinet_fortiproxy/docs/knowledge_base/service_info.md | 146 | Elastic.DontUse | Don't use 'and/or'. |
💡 Suggestions (7)
| File | Line | Rule | Message |
|---|---|---|---|
| packages/fortinet_fortiproxy/_dev/build/docs/README.md | 48 | Elastic.FirstPerson | Avoid first-person pronouns such as ' I '. |
| packages/fortinet_fortiproxy/_dev/build/docs/README.md | 62 | Elastic.FirstPerson | Avoid first-person pronouns such as ' I '. |
| packages/fortinet_fortiproxy/docs/README.md | 20 | Elastic.Versions | Use 'later versions' instead of 'Newer versions' when referring to versions. |
| packages/fortinet_fortiproxy/docs/README.md | 48 | Elastic.FirstPerson | Avoid first-person pronouns such as ' I '. |
| packages/fortinet_fortiproxy/docs/README.md | 58 | Elastic.Versions | Use 'or later' instead of 'or higher' when referring to versions. |
| packages/fortinet_fortiproxy/docs/README.md | 62 | Elastic.FirstPerson | Avoid first-person pronouns such as ' I '. |
| packages/fortinet_fortiproxy/docs/README.md | 200 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
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.
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
cc @mjwolf |
vinit-chauhan
approved these changes
Feb 24, 2026
|
Package fortinet_fortiproxy - 1.4.0 containing this change is available at https://epr.elastic.co/package/fortinet_fortiproxy/1.4.0/ |
ilyannn
pushed a commit
that referenced
this pull request
Feb 28, 2026
* [fortinet_fortiproxy] Update Fortinet FortiProxy documentation Update documentation for the fortinet_fortiproxy integration. This expands the information on the use-cases supported by the integration, and the data collected. It also reformats the set up instructions to make them easier to follow, and adds common troubleshooting issues. Assisted by Google Gemini * Update changelog, and fix lint warnings * Update validation * Update disclaimer
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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_fortiproxy integration. This expands the information on the use-cases supported by the integration, and the data collected. It also reformats the set up instructions to make them easier to follow, and adds common troubleshooting issues.
Assisted by Google Gemini
Checklist
changelog.ymlfile.