[Iptables] update documentation

[haetamoudi]

Proposed commit message

[iptables] Documentation Update

generated new knowledge base file
generated new documentation

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

[github-actions]

Vale Linting Results

Summary: 13 warnings, 15 suggestions found

⚠️ Warnings (13)

File	Line	Rule	Message
packages/iptables/docs/README.md	207	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/iptables/docs/README.md	219	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/iptables/docs/README.md	234	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/iptables/docs/README.md	294	Elastic.DontUse	Don't use 'Note that'.
packages/iptables/docs/README.md	294	Elastic.DontUse	Don't use 'note that'.
packages/iptables/docs/README.md	294	Elastic.DontUse	Don't use 'note that'.
packages/iptables/docs/README.md	354	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/iptables/docs/README.md	355	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/iptables/docs/README.md	356	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/iptables/docs/README.md	356	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/iptables/docs/README.md	357	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/iptables/docs/README.md	357	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/iptables/docs/knowledge_base/service_info.md	50	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.

💡 Suggestions (15)

File	Line	Rule	Message
packages/iptables/_dev/build/docs/README.md	112	Elastic.HeadingColons	Capitalize ': u'.
packages/iptables/_dev/build/docs/README.md	123	Elastic.HeadingColons	Capitalize ': l'.
packages/iptables/_dev/build/docs/README.md	132	Elastic.HeadingColons	Capitalize ': j'.
packages/iptables/docs/README.md	112	Elastic.HeadingColons	Capitalize ': u'.
packages/iptables/docs/README.md	123	Elastic.HeadingColons	Capitalize ': l'.
packages/iptables/docs/README.md	132	Elastic.HeadingColons	Capitalize ': j'.
packages/iptables/docs/README.md	289	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/iptables/docs/README.md	294	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
packages/iptables/docs/README.md	294	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/iptables/docs/README.md	342	Elastic.WordChoice	Consider using 'start, run' instead of 'boot', unless the term is in the UI.
packages/iptables/docs/README.md	342	Elastic.WordChoice	Consider using 'start, run' instead of 'boot', unless the term is in the UI.
packages/iptables/docs/README.md	361	Elastic.Wordiness	Consider using 'all' instead of 'All of '.
packages/iptables/docs/knowledge_base/service_info.md	80	Elastic.HeadingColons	Capitalize ': u'.
packages/iptables/docs/knowledge_base/service_info.md	92	Elastic.HeadingColons	Capitalize ': l'.
packages/iptables/docs/knowledge_base/service_info.md	101	Elastic.HeadingColons	Capitalize ': j'.

---

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.

[elasticmachine]

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

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[mjwolf]

Thanks! this looks good to me. We're still deciding on the wording of a disclaimer that will be added to these, so I'll wait for that to be decided before approving this

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 286454c

History

• 💚 Build #38076 succeeded ab8d9f9
• 💚 Build #37941 succeeded 6a41ab8
• 💚 Build #37874 succeeded 6ff4820

[elastic-vault-github-plugin-prod]

Package iptables - 1.23.0 containing this change is available at https://epr.elastic.co/package/iptables/1.23.0/