Skip to content

[Cisco Nexus] update documentation ( LLM Generated ) - #17289

Merged
vinit-chauhan merged 7 commits into
elastic:mainfrom
vinit-chauhan:cisco_nexus-update_documentation
Feb 19, 2026
Merged

[Cisco Nexus] update documentation ( LLM Generated )#17289
vinit-chauhan merged 7 commits into
elastic:mainfrom
vinit-chauhan:cisco_nexus-update_documentation

Conversation

@vinit-chauhan

@vinit-chauhan vinit-chauhan commented Feb 6, 2026

Copy link
Copy Markdown
Contributor

Proposed commit message

[cisco_nexus] added knowledge_base file and generated README using llm based tooling

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

image
@vinit-chauhan vinit-chauhan self-assigned this Feb 6, 2026
@vinit-chauhan vinit-chauhan added documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. Integration:cisco_nexus Cisco Nexus Team:Integration-Experience Security Integrations Integration Experience [elastic/integration-experience] labels Feb 6, 2026
@github-actions

github-actions Bot commented Feb 6, 2026

Copy link
Copy Markdown
Contributor

Vale Linting Results

Summary: 29 warnings, 12 suggestions found

⚠️ Warnings (29)
File Line Rule Message
packages/cisco_nexus/_dev/build/docs/README.md 21 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/_dev/build/docs/README.md 47 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/_dev/build/docs/README.md 66 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/_dev/build/docs/README.md 76 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/_dev/build/docs/README.md 140 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/cisco_nexus/_dev/build/docs/README.md 155 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/cisco_nexus/_dev/build/docs/README.md 186 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/cisco_nexus/docs/README.md 21 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/docs/README.md 47 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/docs/README.md 66 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/docs/README.md 76 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/docs/README.md 140 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/cisco_nexus/docs/README.md 155 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/cisco_nexus/docs/README.md 186 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/cisco_nexus/docs/README.md 243 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/docs/README.md 256 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/docs/README.md 278 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/cisco_nexus/docs/README.md 298 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/docs/knowledge_base/service_info.md 53 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/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/cisco_nexus/docs/knowledge_base/service_info.md 105 Elastic.EndPuntuaction Don't end headings with punctuation.
packages/cisco_nexus/docs/knowledge_base/service_info.md 106 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/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/cisco_nexus/docs/knowledge_base/service_info.md 118 Elastic.EndPuntuaction Don't end headings with punctuation.
packages/cisco_nexus/docs/knowledge_base/service_info.md 119 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/docs/knowledge_base/service_info.md 130 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/docs/knowledge_base/service_info.md 130 Elastic.EndPuntuaction Don't end headings with punctuation.
packages/cisco_nexus/docs/knowledge_base/service_info.md 131 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/cisco_nexus/docs/knowledge_base/service_info.md 158 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
💡 Suggestions (12)
File Line Rule Message
packages/cisco_nexus/_dev/build/docs/README.md 26 Elastic.WordChoice Consider using 'start, run' instead of 'boot', unless the term is in the UI.
packages/cisco_nexus/_dev/build/docs/README.md 40 Elastic.FirstPerson Avoid first-person pronouns such as ' I '.
packages/cisco_nexus/_dev/build/docs/README.md 60 Elastic.FirstPerson Avoid first-person pronouns such as ' I '.
packages/cisco_nexus/_dev/build/docs/README.md 145 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/cisco_nexus/_dev/build/docs/README.md 163 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/cisco_nexus/_dev/build/docs/README.md 175 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/cisco_nexus/docs/README.md 26 Elastic.WordChoice Consider using 'start, run' instead of 'boot', unless the term is in the UI.
packages/cisco_nexus/docs/README.md 40 Elastic.FirstPerson Avoid first-person pronouns such as ' I '.
packages/cisco_nexus/docs/README.md 60 Elastic.FirstPerson Avoid first-person pronouns such as ' I '.
packages/cisco_nexus/docs/README.md 145 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/cisco_nexus/docs/README.md 163 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/cisco_nexus/docs/README.md 175 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.
@vinit-chauhan @claude
Fix Vale linting issues in cisco_nexus documentation
395354d 
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@vinit-chauhan
vinit-chauhan marked this pull request as ready for review February 10, 2026 18:32
@vinit-chauhan
vinit-chauhan requested a review from a team as a code owner February 10, 2026 18:32
@elasticmachine

elasticmachine commented Feb 10, 2026

Copy link
Copy Markdown

Pinging @elastic/integration-experience (Team:Integration-Experience)
@mjwolf mjwolf added the enhancement New feature or request label Feb 10, 2026
mjwolf
mjwolf reviewed Feb 10, 2026
View reviewed changes
Comment thread packages/cisco_nexus/_dev/build/docs/README.md Outdated
The [Cisco Nexus](https://www.cisco.com/c/en_my/products/switches/data-center-switches/index.html) integration allows users to monitor Errors and System Messages. The Cisco Nexus series switches are modular and fixed port network switches designed for the data center. All switches in the Nexus range run the modular NX-OS firmware/operating system on the fabric. NX-OS has some high-availability features compared to the well-known Cisco IOS. This platform is optimized for high-density 10 Gigabit Ethernet.
The Cisco Nexus integration for Elastic enables you to collect and parse system messages and error logs from Cisco Nexus series switches running NX-OS. These modular and fixed-port network switches are designed for data center environments, and this integration provides critical visibility into the operational health and security status of your networking infrastructure.

This integration facilitates:

@mjwolf mjwolf Feb 10, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

These points are also in the "Supported Use Cases" section. I think you could remove them here
@vinit-chauhan

vinit-chauhan commented Feb 19, 2026

Copy link
Copy Markdown
Contributor Author

/test
@elastic-vault-github-plugin-prod

elastic-vault-github-plugin-prod Bot commented Feb 19, 2026

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport
@elasticmachine

elasticmachine commented Feb 19, 2026

Copy link
Copy Markdown

💚 Build Succeeded

History

cc @vinit-chauhan
@vinit-chauhan
vinit-chauhan merged commit 677150b into elastic:main Feb 19, 2026
11 checks passed
@elastic-vault-github-plugin-prod

elastic-vault-github-plugin-prod Bot commented Feb 19, 2026

Copy link
Copy Markdown
Contributor

Package cisco_nexus - 1.6.0 containing this change is available at https://epr.elastic.co/package/cisco_nexus/1.6.0/
navnit-elastic pushed a commit to navnit-elastic/integrations that referenced this pull request Mar 2, 2026
@vinit-chauhan Navnit Chauhan
[Cisco Nexus] update documentation ( LLM Generated ) (elastic#17289)
14ac4f4 
* Update documentation for the integration.

* update pr link in changelog

* Fix Vale linting issues in cisco_nexus documentation

* fix few more Vale issues

* Add document structure validation

* update ai-generation note
@vinit-chauhan
vinit-chauhan deleted the cisco_nexus-update_documentation branch April 1, 2026 23:58
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:cisco_nexus Cisco Nexus Team:Integration-Experience Security Integrations Integration Experience [elastic/integration-experience]

3 participants

@vinit-chauhan @elasticmachine @mjwolf