Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[mongodbatlasreceiver] Add support to collect Organization Events #20308

Closed
JonathanWamsley opened this issue Mar 24, 2023 · 3 comments
Closed
Assignees
Labels

Comments

@JonathanWamsley
Copy link
Contributor

JonathanWamsley commented Mar 24, 2023

Component(s)

receiver/mongodbatlas

Is your feature request related to a problem? Please describe.

The current Mongodb Atlas receiver already supports Project events, but it would be a great addition to also support Organization events as mentioned here.

Each organization events have occurred within a specific timeframe and contain useful information. This useful information can be used for monitoring the health and performance of clusters, troubleshooting cluster issues by identifying organization events that may be the source of the problem or auditing all changes and activities in your MongoDB Atlas Organization.

Describe the solution you'd like

Organization events can be obtained from the this API endpoint:
GET /orgs/{ORG-ID}/events

This request path requires a parameter ORG-ID for the organization similar to how the Project event requires GROUP-ID. The request query parameters and response output of the org events and the project events are the same, so a lot of code from project events can be reused.

I suggest following a similar format for the config by including an org event and a name which, is a list of each organization event to be collected.

A sample config to collect both events would look like:

mongodbatlas:
  public_key: "my-public-key"
  private_key: "my-private-key"
  events:
    projects:
      - name: Project 0
        include_clusters: [Cluster0]
    orgs:
      - id: Orgid
        include_clusters: [Cluster0]
    poll_interval: 1m
    page_size: 100
    max_pages: 25

The PollInterval, types, pageSize and maxpages would be shared across events. Each specified organization or project will have their own org/project config similar to how the current ProjectConfig is implmented.

Describe alternatives you've considered

Not sure if orgs in the config is preferred over organizations

Additional context

I'll be happy to implement this feature.

@JonathanWamsley JonathanWamsley added enhancement New feature or request needs triage New item requiring triage labels Mar 24, 2023
@github-actions
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@atoulme atoulme added receiver/mongodbatlas and removed needs triage New item requiring triage labels Mar 24, 2023
@github-actions
Copy link
Contributor

Pinging code owners for receiver/mongodbatlas: @djaglowski @schmikei. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@JonathanWamsley
Copy link
Contributor Author

resolved with #20343

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants