https://support.atlassian.com/opsgenie/docs/what-are-the-integration-types-and-actions/
...
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
The integrations Framework allows Jira Service Management’s alerting capability to work in conjunction with the most popular IT, operations management, and monitoring tools. Through email and API, Jira Service Management can communicate with these tools and process its alerts according to the data they send. With integrations, you can extend your everyday monitoring services with a powerful alert and notification system. Jira Service Management integrates with the services RackspaceGitHub, New Relic, CirconusServerGuard24, and more.
Jira Service Management gives you a robust framework so that you can integrate it with all your operations management tools. Through email and APIs, Jira Service Management can communicate with your tools.
View the full list of Jira Service Management integrations.
...
...
The owner of your Jira Service Management account has to verify emails of users within your organization so that they can use API integrations.
Integration
...
types
...
API-based
...
integrations
You can forward events from many monitoring tools to Jira Service Management for alerting purposes. Jira Service Management is able to can catch and process notification webhooks and create well-informed alerts based on the notification data. With this ability, you can let Jira Service Management process any HTTP request as well as using many API-based integrations configured specifically for monitoring tools. For example, if you're a Scout Raygun customer, you can use Jira Service Management's Scout the Raygun Integration to let Jira Service Management automatically create and close alerts according to events on Scout.
| Info |
|---|
The owner of your Jira Service Management account has to verify emails of users within your organization so that they can use API integrations. |
...
Jira Service Management's bidirectional in Raygun.
Bidirectional integrations
Bidirectional integrations allow data to be sent and processed both ways between Jira Service Management and the other applications. A good example is our ServiceNow integration . Using the integration, - ServiceNow sends incident events to Jira Service Management , with detailed information and Jira Service Management forwards alerts as incidents to ServiceNow.
Outgoing
...
integrations
The Jira Service Management Integrations Framework integrations framework has a callback capability that can notify chat applications about Jira Service Management events. A good outgoing integration example is our Webhook capabilities which pushes push information via a URL endpoint. It's important to note that this information is not customizable
Email-based Integrations
You can use Jira Service Management email integrations to process your incoming emails for alert management. Jira Service Management Email Integration This integration accepts any kind of email and is fully customizable ; allowing you to control a robust alerting mechanism tailored to your inbox. Jira Service Management also has also specific email-based integrations for several monitoring tools, e.g., for example: Pingdom, Uptime Robot, Zenoss etc. For example, if you're a Pingdom customer, you can add Jira Service Management's Pingdom Integration integration and readily turn Pingdom events into Jira Service Management alerts.
| Info |
|---|
Share your feedbackWe would love to receive feedback about this documentation, the product experience, functionality, or anything you’ve got to share. (Simpler: Do you have any feedback about this documentation, your product experience, or any functionality? We'd love to hear from you.) You can either add comments to this page or add a card on the Trello board. |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Criteria for checks |
- Replacing OG with JSM
- Basic grammar & spell check
- US English
- Positive language
- Removing passive voice (wherever necessary)
- Simplifying sentences
- Change V&T
- Replacing old links and images with new ones
- Structure of these pages: Do these need to be separate topics? Can it be added /merged with another topic? Does the headline need to revised? Are all the topics + content helpful for our reader?
- Conceptual validation: Do these journeys, concepts, terms make sense for JSM? Do we need a developer to verify parts of this content?