[Fortinet_Fortimanager] Update fortinet fortimanager

[robester0403]

Proposed commit message

[Fortinet_Fortimanager] Documentation Update

generated new knowledge base file
generated new documentation

Please explain:

• WHAT: patterns used, algorithms implemented, design architecture, message processing, etc.
• WHY: the rationale/motivation for the changes

This text will be pasted into the squash dialog when the change is committed and will be
a long term historical record of the change to help future contributors understand the
change, please help them by making it clear and comprehensive, they may be you.

If the commit title is adequate to describe both of these things, The text here may be omitted
or replaced with "See title". The title of the PR will be used as the commit message title when
the merge is made and the "See title" marker will be removed if present.

The text here and the PR title will be subject to the PR review process.
-->

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

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[github-actions]

Vale Linting Results

Summary: 39 warnings, 8 suggestions found

⚠️ Warnings (39)

File	Line	Rule	Message
packages/fortinet_fortimanager/_dev/build/docs/README.md	62	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/_dev/build/docs/README.md	84	Elastic.DontUse	Don't use 'just'.
packages/fortinet_fortimanager/_dev/build/docs/README.md	84	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/_dev/build/docs/README.md	86	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/_dev/build/docs/README.md	137	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortimanager/_dev/build/docs/README.md	138	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortimanager/_dev/build/docs/README.md	224	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/_dev/build/docs/README.md	226	Elastic.DontUse	Don't use 'very'.
packages/fortinet_fortimanager/docs/README.md	62	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/README.md	84	Elastic.DontUse	Don't use 'just'.
packages/fortinet_fortimanager/docs/README.md	84	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/README.md	86	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/README.md	137	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortimanager/docs/README.md	138	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortimanager/docs/README.md	224	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/README.md	226	Elastic.DontUse	Don't use 'very'.
packages/fortinet_fortimanager/docs/README.md	243	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/README.md	256	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/README.md	278	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortimanager/docs/README.md	298	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	33	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	34	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	66	Elastic.DontUse	Don't use 'just'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	66	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	68	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	110	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	110	Elastic.EndPuntuaction	Don't end headings with punctuation.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	111	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/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_fortimanager/docs/knowledge_base/service_info.md	121	Elastic.EndPuntuaction	Don't end headings with punctuation.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	122	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	161	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	162	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	169	Elastic.EndPuntuaction	Don't end headings with punctuation.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	193	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	194	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	195	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	207	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	209	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'versus' instead of 'vs'.

💡 Suggestions (8)

File	Line	Rule	Message
packages/fortinet_fortimanager/_dev/build/docs/README.md	111	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/fortinet_fortimanager/_dev/build/docs/README.md	203	Elastic.WordChoice	Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
packages/fortinet_fortimanager/docs/README.md	111	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/fortinet_fortimanager/docs/README.md	203	Elastic.WordChoice	Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	43	Elastic.Versions	Use 'or later' instead of 'or newer' when referring to versions.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	94	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	158	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
packages/fortinet_fortimanager/docs/knowledge_base/service_info.md	225	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', 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.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

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

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: dd035b7

History

• 💚 Build #37999 succeeded 9e78e1a

[vinit-chauhan]

We can omit default values which are only placeholders. ex. SSL Configs, Custom TCP Options.