elastic / elastic/integrations

[MongoDB Atlas]: Multiple Group/Project IDs per Integration Policy

Open
#17,407 1 comment 0 reactions 0 assignees View on GitHub
Integration:mongodb_atlas needs:triage Team:Obs-InfraObs
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
3d 4h
Merged PRs (30d)
209

Description

### Integration Name

MongoDB Atlas [mongodb_atlas]

### Dataset Name

_No response_

### Integration Version

1.1.0

### Agent Version

9.2.4

### OS Version and Architecture

Elastic Managed Cloud via GCP

### User Goal

We are currently trying to integrate logs from our MongoDB Atlas System, via the Integration, into our SIEM. Our Setup might be a "little" special here so I make sure to explain it as clean as I can:

MongoDB Atlas has the functionalility to create multiple organisations in the "Atlas". These organisation can contain multiple groups and projects. The Integration is built in a way where we would need to deply a lot of policies 50+ in our case to get the data we need. Is it possible to build the Integration in a way, where multiple group- and orgids can be configured during policy creation?

If the Integration would allow for more groups to be entered, we could limit our deplyoed MongoDB Atlas integrations to the max. Number of organisation we have. Our Goal is basically to have one MongoDB Atlas Integration/Policy per Organization that we have at MongoDB. Now there would be over 50+ because of all the DBs and Orgs in use.

### Existing Features

Due to the MongoDB Atlas setup we'd need to deploy *a lot* of Integrations and subsequent policies to gather all the data we need.

### What did you see?

Per Integraiton policy only one org and group can be entered at the same time.

### Anything else?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.