Manual Alert Updates and the Default API Integration

[#1]

Summary

When making updates to Opsgenie/JSM Operation Alerts you will see that when you manually interact with Alerts in the UI, or using the REST API it will go through the Default API Integration always. But why is that the case? Why is the Default API Integration chosen here?

Example Situations

• Alerts are not being auto-actions when making updates through your expected API Integration.
• Alerts are being created without a Responder
• No notifications sent out/no alert created for data sent into Opsgenie/JSM Operations

Explanation

Opsgenie uses the default API integration for manual alert updates primarily for flexibility and ease of use. The default API integration is a special global integration that is created by default when a customer account is established and cannot be deleted. This ensures that users always have the ability to create alerts manually through the Opsgenie user interface (UI), even if no other API integrations are configured. This integration cannot be owned by a specific team, making it universally accessible for creating alerts manually across the organization.

That being said, the default API integration is crucial for manual alert creation because it allows for the dynamic selection of responders based on the specific situation at hand. When creating an alert manually, users can specify the API integration, alert message, priority, and responders, ensuring that the right teams or individuals are notified promptly. This process is designed to be straightforward, allowing for quick and efficient alert creation to mobilize the necessary response teams or individuals.

Lastly, the default API integration supports the inclusion of dynamic fields and string processing methods, enabling users to customize alert fields and extract specific data from payloads. This capability enhances the richness and informativeness of alerts, providing responders with the context needed for an effective response. The integration's design to be global and not team-specific ensures that it remains a versatile tool for manual alert creation, supporting a wide range of use cases and operational requirements within an organization.

So in short, the Default API Integration provides a great range of flexibility with all other API endpoints used with OG/JSM Ops. 

Please note that the Default API Integration that is created by Opsgenie should not be updated as that is the global Default API Integration and all manual and programmatic API calls to that endpoint will go through that integration. It is best to not edit the default one but to create new ones on top of the default system API Integration

Restrictions

• Default API integration name can not be changed.

• Default API integration can not be disabled & deleted.

Related Articles

• What is the Default API Integration 
• How are Alerts Created? 
• String processing methods in Opsgenie integrations 
• Dynamic fields in Opsgenie integrations

Hope this helps add more context!  

Cheers,

Christian