- API >
- Public API Resources >
- Measurements and Alerts >
- Third-Party Integration Settings >
- Update a Configuration for a Third-Party Service Integration
Update a Configuration for a Third-Party Service Integration¶
On this page
Note
Groups and projects are synonymous terms. Your {PROJECT-ID}
is the
same as your project id. For existing groups, your group/project id
remains the same. This page uses the more familiar term group when
referring to descriptions. The endpoint remains as stated in the
document.
Base URL: https://cloud.mongodb.com/api/public/v1.0
Syntax¶
Request Path Parameters¶
Parameter | Necessity | Description |
---|---|---|
{PROJECT-ID} |
Required | Project identifier. |
{INTEGRATION-TYPE} |
Required | Third-party service identifier. Accepted values are:
|
Request Query Parameters¶
Name | Type | Necessity | Description | Default |
---|---|---|---|---|
pageNum | number | Optional | One-based integer that returns a subsection of results. | 1 |
itemsPerPage | number | Optional | Number of items to return per page, up to a maximum of 500. | 100 |
pretty | boolean | Optional | Flag that indicates whether the response body should be in a prettyprint format. | false |
envelope | boolean | Optional | Flag that indicates whether or not to wrap the response in an envelope. Some API clients cannot access the HTTP response headers or
status code. To remediate this, set For endpoints that return a list of results, the |
false |
Request Body Parameters¶
The request body should be a single integration view (like a JSON
configuration object) for a single third-party service. If a
configuration of the same type
already exists, the request will
update the changed fields. If a configuration of the same type
does
not exist, it will be added. Always include a type
property equal
to the third-party service INTEGRATION_TYPE
.
Service | Configuration Options | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
PagerDuty | You must provide the following fields when you configure a PagerDuty integration:
|
||||||||||||
Slack | Important Slack integrations now use the OAuth2 verification method and must be initially configured, or updated from a legacy integration, through the MongoDB Atlas third-party service integrations page. Legacy tokens will soon no longer be supported. You must provide the following fields when you reconfigure an existing Slack integration:
You may also include the following fields:
|
||||||||||||
New Relic | You must provide the following fields when you configure a New Relic integration: Important Effective Wednesday, June 16th, 2021, New Relic no longer supports the plugin-based integration with MongoDB. We do not recommend that you sign up for the plugin-based integration. To learn more, see the New Relic Plugin EOL Statement. As an alternative, consider New Relic’s MongoDB monitoring integration.
|
||||||||||||
Opsgenie | You must provide the following fields when you configure a Opsgenie integration:
|
||||||||||||
VictorOps | You must provide the following fields when you configure a VictorOps integration:
You may also include the following fields:
|
||||||||||||
Flowdock | You must provide the following fields when you configure a VictorOps integration:
|
||||||||||||
Webhook Settings | You must provide the following fields when you configure webhook settings:
You may also include the following fields:
|
Response Elements¶
The response includes a results
array which lists all third-party
integration configurations for the project as objects, and a
totalCount
of the services integrated with the project.
Each third-party integration configuration object includes a type
property equal to its own integration type ("type":
"PAGER_DUTY"
for the PagerDuty service). Additionally, each
third-party service configuration object provides details specific to
that service. The following lists the properties returned for each
third-party service configuration object:
Service | Result | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
PagerDuty | A returned PagerDuty integration configuration object contains the following fields:
|
||||||||||||
Slack | A returned Slack integration configuration object contains the following fields:
|
||||||||||||
New Relic | A returned New Relic integration configuration object contains the following fields: Important Effective Wednesday, June 16th, 2021, New Relic no longer supports the plugin-based integration with MongoDB. We do not recommend that you sign up for the plugin-based integration. To learn more, see the New Relic Plugin EOL Statement. As an alternative, consider New Relic’s MongoDB monitoring integration.
|
||||||||||||
Opsgenie | A returned Opsgenie integration configuration object contains the following fields:
|
||||||||||||
VictorOps | A returned VictorOps integration configuration object contains the following fields:
The configuration object may also contain the following fields, depending on your configuration:
|
||||||||||||
Flowdock | A returned Flowdock integration configuration object contains the following fields:
|
||||||||||||
Webhook Settings | A returned webhook configuration object contains the following fields:
The configuration object may also contain the following fields, depending on your configuration:
|