Skip to content

[mongodb_atlas] Enable Agentless deployment.#18507

Merged
ritalwar merged 5 commits intoelastic:mainfrom
ritalwar:mongodb_atlas_enable_agentless
Apr 24, 2026
Merged

[mongodb_atlas] Enable Agentless deployment.#18507
ritalwar merged 5 commits intoelastic:mainfrom
ritalwar:mongodb_atlas_enable_agentless

Conversation

@ritalwar
Copy link
Copy Markdown
Contributor

  • Enhancement

Proposed commit message

Enable Agentless deployment mode for Mongodb_Atlas integration package.

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

@ritalwar ritalwar requested a review from a team as a code owner April 17, 2026 15:17
@ritalwar ritalwar self-assigned this Apr 17, 2026
@ritalwar ritalwar added integration Label used for meta issues tracking each integration Integration:mongodb_atlas MongoDB Atlas Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations] labels Apr 17, 2026
Comment thread packages/mongodb_atlas/changelog.yml Outdated
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 17, 2026

Vale Linting Results

Summary: 2 suggestions found

💡 Suggestions (2)
File Line Rule Message
packages/mongodb_atlas/_dev/build/docs/README.md 31 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/mongodb_atlas/docs/README.md 31 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.

Updated link for version 1.2.0 to point to the relevant PR.
@andrewkroh andrewkroh added the documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. label Apr 17, 2026
@ritalwar ritalwar requested a review from ishleenk17 April 22, 2026 08:07
@elastic-vault-github-plugin-prod
Copy link
Copy Markdown

elastic-vault-github-plugin-prod Bot commented Apr 22, 2026

🚀 Benchmarks report

Package mongodb_atlas 👍(1) 💚(0) 💔(7)

Expand to view
Data stream Previous EPS New EPS Diff (%) Result
alert 4347.83 2155.17 -2192.66 (-50.43%) 💔
disk 27777.78 14705.88 -13071.9 (-47.06%) 💔
hardware 26315.79 16949.15 -9366.64 (-35.59%) 💔
mongod_audit 8333.33 5813.95 -2519.38 (-30.23%) 💔
mongod_database 25641.03 11627.91 -14013.12 (-54.65%) 💔
process 5235.6 1647.45 -3588.15 (-68.53%) 💔
project 4366.81 3676.47 -690.34 (-15.81%) 💔

To see the full report comment with /test benchmark fullreport

Comment on lines +33 to +37
## Agentless Enabled Integration

Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to [Agentless integrations](https://www.elastic.co/guide/en/serverless/current/security-agentless-integrations.html) and the [Agentless integrations FAQ](https://www.elastic.co/guide/en/serverless/current/agentless-integration-troubleshooting.html).
Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features.

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.

Please follow the approach we already took to be consistent across the integrations

## How do I deploy this integration?

### Agent-based deployment

Elastic Agent must be installed. For more details, check the Elastic Agent [installation instructions](https://www.elastic.co/docs/reference/fleet/install-elastic-agents). You can install only one Elastic Agent per host.

Elastic Agent is required to collect data from Mongo and ship the data to Elastic, where the events will then be processed via the integration's ingest pipelines.

### Agentless deployment

Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to [Agentless integrations](https://www.elastic.co/guide/en/serverless/current/security-agentless-integrations.html)

Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features.

cc: https://github.com/elastic/integrations/blob/main/packages/aws/docs/sqs.md?plain=1#L29-L42

Comment thread packages/mongodb_atlas/validation.yml
@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

History

cc @ritalwar

@ritalwar ritalwar merged commit 9722c93 into elastic:main Apr 24, 2026
13 checks passed
@elastic-vault-github-plugin-prod
Copy link
Copy Markdown

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

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. Integration:mongodb_atlas MongoDB Atlas integration Label used for meta issues tracking each integration Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants