Skip to content

Update Elastic Managed integration documentation wording and links - #20987

Open
moxarth-rathod wants to merge 5 commits into
elastic:mainfrom
moxarth-rathod:agentless-update
Open

Update Elastic Managed integration documentation wording and links#20987
moxarth-rathod wants to merge 5 commits into
elastic:mainfrom
moxarth-rathod:agentless-update

Conversation

@moxarth-rathod

@moxarth-rathod moxarth-rathod commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Proposed commit message

Update Elastic Managed integration documentation wording and links.

Replace the Elastic Managed documentation section in packages that support 
Elastic Managed deployments.

The previous copy described the feature as collecting data without managing Elastic Agent 
and linked to the old Serverless agentless guides. The updated text states that Elastic Managed
 integrations are supported only on Elastic Cloud Serverless and Elastic Cloud Hosted, 
that Elastic runs the collector, and it points to the current Managed integrations docs and FAQ.

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

Related issues

Co-authored-by: Cursor <cursoragent@cursor.com>
@moxarth-rathod moxarth-rathod self-assigned this Sep 1, 2026
@moxarth-rathod moxarth-rathod added documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. enhancement New feature or request Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] Team:SDE-Crest Crest developers on the Security Integrations team [elastic/sit-crest-contractors] agentless Agentless related issues labels Sep 1, 2026
@moxarth-rathod
moxarth-rathod requested a review from a team as a code owner September 1, 2026 06:47
@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs Style Checker (Vale)

Summary: 9 warnings, 9 suggestions found

⚠️ Warnings (9): Fix when the suggestion improves clarity or correctness.
File Line Rule Message
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 50 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 50 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'that is' instead of 'i.e'.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 148 Elastic.MenuArrowsBold Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 148 Elastic.MenuArrows Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 156 Elastic.MenuArrowsBold Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 156 Elastic.MenuArrows Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 187 Elastic.DontUse Don't use 'please'. Choose a more precise or reader-focused term.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 188 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 188 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
💡 Suggestions (9): Optional style improvements. Apply when helpful.
File Line Rule Message
packages/tenable_sc/_dev/build/docs/README.md 26 Elastic.Wordiness Consider using 'per' instead of 'as per'.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 26 Elastic.Versions Use 'and later' instead of 'and newer' when referring to versions.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 90 Elastic.WordChoice Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 100 Elastic.WordChoice Consider using 'run, start' instead of 'execute', unless the term is in the UI.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 112 Elastic.Wordiness Consider using 'all' instead of 'all of '.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 112 Elastic.Versions Use 'earlier versions' instead of 'older versions' when referring to versions.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md 134 Elastic.Wordiness Consider using 'per' instead of 'as per'.
packages/ti_socradar_feeds/_dev/build/docs/README.md 32 Elastic.Semicolons Use semicolons sparingly. Consider splitting the sentence or using a comma or conjunction.
packages/ti_socradar_taxii/_dev/build/docs/README.md 32 Elastic.Semicolons Use semicolons sparingly. Consider splitting the sentence or using a comma or conjunction.

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.

@andsel andsel left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

#18627 is effectively an issue and not a PR

Comment thread packages/logstash/changelog.yml Outdated
- description: Fix status colour mappings in Node Health and Pipeline Health dashboards so that red/yellow/green/unknown statuses render with correct colours using the Borealis palette.
type: bugfix
link: https://github.com/elastic/integrations/issues/18627
link: https://github.com/elastic/integrations/pull/18627

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@moxarth-rathod
#18627 is the issue that's solved by #19334. So this change seems not good.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Thanks @andsel for highlighting this, I've reverted this change. It was unintentionally included as part of the bulk updates.

@efd6 efd6 Sep 2, 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.

This should be https://github.com/elastic/integrations/pull/19334, not the issue link.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes @efd6, it should be #19334 , but since this change is anyway not related to this PR changes so I reverted that code. Do you want to keep that change in this PR?

@elastic-vault-github-plugin-prod

elastic-vault-github-plugin-prod Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

Comment thread packages/journald/_dev/test/system/test-journald-config.yml Outdated
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

✅ All changelog entries have the correct PR link.

@vera-review-bot

Copy link
Copy Markdown

🟢 Reviewed the latest commits 59aa0e93713c4b (7 commits) — nothing new beyond already posted comments.

A new commit triggers another review — at most once every 15 minutes. I skip the PR while it's approved or has merge conflicts.

🤖 AI-Generated Review | Vera Review Bot - v0.3.0 | 📚 Knowledge base: integration-skills

⚠️ Automated review — verify suggestions before applying.

Comment on lines -40 to 46
{{/* If agentless is available for this integration, we'll want to include that here as well.
### Agentless deployment
{{/* If Elastic Managed integration is available for this integration, we'll want to include that here as well.
### Elastic Managed enabled integration

Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. Agentless deployments provide a means to ingest data while avoiding the orchestration, management, and maintenance needs associated with standard ingest infrastructure. Using an agentless deployment makes manual agent deployment unnecessary, allowing you to focus on your data instead of the agent that collects it.
Elastic Managed integrations are only supported on Elastic Cloud Serverless and Elastic Cloud Hosted deployments. An Elastic Managed integration lets you ingest data from a cloud source while avoiding the orchestration, management, and maintenance associated with standard ingest infrastructure. Elastic runs the collector for you, so you can focus on your data instead of the infrastructure that collects it.

For more information, refer to [Agentless integrations](https://www.elastic.co/guide/en/serverless/current/security-agentless-integrations.html) and [Agentless integrations FAQ](https://www.elastic.co/guide/en/serverless/current/agentless-integration-troubleshooting.html)
For more information, refer to [Elastic Managed integrations](https://www.elastic.co/docs/manage-data/ingest/managed-integrations/managed-integrations) and the [Elastic Managed integrations FAQ](https://www.elastic.co/docs/manage-data/ingest/managed-integrations/managed-integrations-faq).
*/}}

@mrodm mrodm Sep 1, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This documentation comes from the elastic-package repository when elastic-package create package commnad is used:

https://github.com/elastic/elastic-package/blob/2a1e840d0326fc949a0384eefc2afa1c03844736/internal/packages/archetype/_static/package-docs-readme.md.tmpl#L41-L47

@moxarth-rathod Could you update this too in elastic-package repo? so new packages get the new documentation about Elastic Managed enabled integration

As a note, this will take effect in a future elastic-package release version, so there could be new packages with that previous documentation generated in the meantime.

cc @teresaromero

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Just to keep a track of this change, I've opened an issue: elastic/elastic-package#3917

@infra-vault-gh-plugin-prod

infra-vault-gh-plugin-prod Bot commented Sep 2, 2026

Copy link
Copy Markdown

💛 Build succeeded, but was flaky

Failed CI Steps

History

cc @moxarth-rathod

@vera-review-bot

Copy link
Copy Markdown

@moxarth-rathod - This PR has merge conflicts with the base branch. Please resolve them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agentless Agentless related issues documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. enhancement New feature or request Team:SDE-Crest Crest developers on the Security Integrations team [elastic/sit-crest-contractors] Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Agentless] README Still Marks Agentless as Beta While Manifest has release: ga

5 participants