You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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 supportOrganization 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 requiresGROUP-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:
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 overorganizations
Additional context
I'll be happy to implement this feature.
The text was updated successfully, but these errors were encountered: