Integrate Opsgenie with Jira Service Management | Opsgenie | Atlassian Support (2022)

What does Opsgenie offer Jira Service Management users?

Opsgenie provides a powerful two-way integration with Jira Service Management. When a new issue is created in Jira Service Management, a corresponding Opsgenie alert is automatically created, containing rich information about the issue. Opsgenie provides rich notifications with on-call rotations, scheduling features, and alert escalations to ensure the best alert and incident management for Jira Service Management customers. As users execute actions on the alerts, like acknowledge or snooze, the issue in Jira Service Management automatically updates with comments about these alert actions. If users close the alert, the issue in Jira Service Management is resolved (Only if the issue has aResolve the issuetransition).

Functionality of the integration

Jira Service Management to Opsgenie:

  • When an issue is created in Jira Service Management, an alert is created in Opsgenie.

  • When a comment is added to issue in Jira Service Management, the same comment is added as a note to the alert in Opsgenie.

  • When an issue is closed and resolved in Jira Service Management, the alert in Opsgenie is closed.

Opsgenie to Jira Service Management:

  • IfSend Alert Updates Back to Jira Service Managementis enabled, actions for Jira Service Management are executed in Jira Service Management when the chosen action is executed in Opsgenie for alerts which are created by the Jira Service Management integration.

  • IfCreate Jira Service Management Issues for Opsgenie Alertsis enabled, actions for Jira Service Management are executed in Jira Service Management when the chosen action is executed in Opsgenie for alerts which have a source other than the Jira Service Management integration.

  • This action mapping features are explained in detail in theAction Mapping Featuresection below.

Adding Jira Service Management Integration in Opsgenie

You can add this integration from your team dashboard

If you're using Opsgenie'sFreeorEssentialsplan, or if you’re using Opsgenie with Jira Service Management'sStandardplan, you can only add this integration from your team dashboard as the Integrations page under Settings is not available in your plan.

Adding the integration from your team dashboard will make your team the owner of the integration. This means Opsgenie will assign the alerts received through this integration to your team only.

To do that,

  1. Go to your team’s dashboard from Teams,

    (Video) Integrating Opsgenie and Jira Service Desk

  2. Select Integrations, and selectAdd integration.

Follow the rest of the steps to complete the integration.

  1. Go to Settings > Integrations. Search for Jira Service Management and select Add.

  2. Specify who is notified of Jira Service Management alerts using theResponders field. Auto-complete suggestions are provided as you type.

  3. Copy the integration URL to use in the Jira Service Management configuration.

  4. ClickSave Integration.

Using SSO?

If you are using SSO to log in to Jira, you need to generate an API token and use this token as the password in the integration settings. VisitManage API tokens for your Atlassian accountto learn how to generate an API token in Jira.

After generating your new token, copy and paste it to the Password field of the Jira integration in Opsgenie. Then, save the integration.

Users who don't have Atlassian Account

Users who are authenticating against the REST API but do not have Atlassian Accounts, need to convert them to Atlassian Account. You can checkhereto see the instructions to convert Atlassian Account.

Action Mapping Feature

  • Opsgenie allows customers to define action mappings between Opsgenie actions and Jira Service Management actions.

  • To use the Action Mappings feature, provide some information to the integration which are listed below:

  • Issue Type Name: The issue types defined in Jira Service Management e.g. Task, IT Help, Sub-task, Service Request or any other custom defined type. Make sure you write the issue type syntax error-free.

  • Jira Service Management URL: This is the domain name of your service e.g.https://testops.atlassian.net

  • Username: The e-mail address you use to login to Jira Service Management.

    (Video) Using Opsgenie On Call with Jira Service Management | Top Tips

  • Password/API Token: The password or API token you use to login to Jira Service Management.

  • Project Key: The key of the project you want to create alerts from e.g. OT, OPS, SIT. The project key is usually in capital letters so make sure you write it in the right form.

For alerts created by Jira Service Management

  • You can use this section to map Opsgenie actions to Jira Service Management actions when the source of the alert is Jira Service Management (i.e When the alert is created by Jira Service Management integration.)

  • You can map different Opsgenie actions to different Jira Service Management actions. For example, you can add note to Jira Service Management issue, when the alert is acknowledged. In order to do this, you should defineIf alert is acknowledged in Opsgenie, add it as a comment to the issue in Jira Service Management. mapping inSend Alert Updates Back to Jira Service Managementsection.

Integrate Opsgenie with Jira Service Management | Opsgenie | Atlassian Support (1)

For other Opsgenie alerts

  • You can use this section to map Opsgenie actions to Jira Service Management actions when the source of the alert isNOTJira Service Management (i.e When the alert is created by another integration.)

  • For this purpose, you can useCreate Jira Service Management Issues for Opsgenie Alertssection. In order to use this functionality, you need to map one Opsgenie action tocreate an issueJira Service Management action. The Opsgenie action doesn't have to bealert is created, it can be other actions as well.

  • a tag is added to the alertanda custom action is executed on alertactions differ from other actions. When one of these actions is selected, an extra field is added to enter for which tags or for which custom action this mapping works.

  • Enter multiple tags by separating the tags with a comma. If multiple tags are entered, the mapping works if the alert has one or more of the specified tags. For the mapping to work for any tag, leave the tags field empty.

  • If an Opsgenie action is mapped to multiple Jira Service Management actions, an error occurs except for thea tag is added to the alertanda custom action is executed on alertactions. Save multiple mappings for these actions because they differ by the given tags and the given custom action names.

Integrate Opsgenie with Jira Service Management | Opsgenie | Atlassian Support (2)

Configuration in Jira Service Management

  1. Log in to Jira as an administrator.

  2. From the dashboard, open the Administration menu. SelectSystem.

  3. From the left, selectWebhooksunder "Advanced".

Integrate Opsgenie with Jira Service Management | Opsgenie | Atlassian Support (3)

4. ClickCreate A Webhook. In the opening section, paste the URL provided by Opsgenie's Jira integration into URL input. ClickCreate.

(Video) The Capabilities of OpsGenie In Jira Service Management

5. Make sure Exclude body checkbox is not selected.

Integrate Opsgenie with Jira Service Management | Opsgenie | Atlassian Support (4)

Integrate Opsgenie with Jira Service Management | Opsgenie | Atlassian Support (5)

Now manage your Jira Service Management alerts at Opsgenie and leverage its full alerting functionality.

Sample payload sent from Jira Service Management

Create Alert payload:

JSON

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297{ "issue": { "id": "10042", "self": "https://test.atlassian.net/rest/api/2/issue/10042", "key": "TEST-43", "fields": { "issuetype": { "self": "https://test.atlassian.net/rest/api/2/issuetype/10000", "id": "10000", "description": "For system outages or incidents. Created by JIRA Service Management.", "iconUrl": "https://test.atlassian.net/servicedesk/issue-type-icons?icon=incident", "name": "Incident", "subtask": false }, "timespent": null, "project": { "self": "https://test.atlassian.net/rest/api/2/project/10000", "id": "10000", "key": "TEST", "name": "Test", "avatarUrls": { "48x48": "https://test.atlassian.net/secure/projectavatar?avatarId=10324", "24x24": "https://test.atlassian.net/secure/projectavatar?size=small&avatarId=10324", "16x16": "https://test.atlassian.net/secure/projectavatar?size=xsmall&avatarId=10324", "32x32": "https://test.atlassian.net/secure/projectavatar?size=medium&avatarId=10324" } }, "fixVersions": [], "aggregatetimespent": null, "resolution": null, "customfield_10027": { "id": "1", "name": "Time to resolution", "_links": { "self": "https://test.atlassian.net/rest/servicedeskapi/request/10042/sla/1" }, "completedCycles": [ { "startTime": { "iso8601": "2016-06-27T11:25:37+0300", "jira": "2016-06-27T11:25:37.877+0300", "friendly": "Today 11:25 AM", "epochMillis": 1467015937877 }, "stopTime": { "iso8601": "2016-06-27T11:37:33+0300", "jira": "2016-06-27T11:37:33.572+0300", "friendly": "Today 11:37 AM", "epochMillis": 1467016653572 }, "breached": false, "goalDuration": { "millis": 14400000, "friendly": "4h" }, "elapsedTime": { "millis": 715695, "friendly": "11m" }, "remainingTime": { "millis": 13684305, "friendly": "3h 48m" } } ], "ongoingCycle": { "startTime": { "iso8601": "2016-06-27T16:01:45+0300", "jira": "2016-06-27T16:01:45.920+0300", "friendly": "Today 4:01 PM", "epochMillis": 1467032505920 }, "breachTime": { "iso8601": "2016-06-28T12:01:45+0300", "jira": "2016-06-28T12:01:45.920+0300", "friendly": "28/Jun/16 12:01 PM", "epochMillis": 1467104505920 }, "breached": false, "paused": false, "withinCalendarHours": true, "goalDuration": { "millis": 14400000, "friendly": "4h" }, "elapsedTime": { "millis": 197118, "friendly": "3m" }, "remainingTime": { "millis": 14202882, "friendly": "3h 56m" } } }, "customfield_10028": { "id": "2", "name": "Time to first response", "_links": { "self": "https://test.atlassian.net/rest/servicedeskapi/request/10042/sla/2" }, "completedCycles": [ { "startTime": { "iso8601": "2016-06-27T11:25:37+0300", "jira": "2016-06-27T11:25:37.877+0300", "friendly": "Today 11:25 AM", "epochMillis": 1467015937877 }, "stopTime": { "iso8601": "2016-06-27T11:37:33+0300", "jira": "2016-06-27T11:37:33.572+0300", "friendly": "Today 11:37 AM", "epochMillis": 1467016653572 }, "breached": false, "goalDuration": { "millis": 14400000, "friendly": "4h" }, "elapsedTime": { "millis": 715695, "friendly": "11m" }, "remainingTime": { "millis": 13684305, "friendly": "3h 48m" } } ] }, "resolutiondate": null, "workratio": -1, "lastViewed": "2016-06-27T16:01:46.447+0300", "watches": { "self": "https://test.atlassian.net/rest/api/2/issue/TEST-43/watchers", "watchCount": 1, "isWatching": true }, "created": "2016-06-27T11:25:37.859+0300", "customfield_10020": "Not started", "customfield_10021": null, "customfield_10022": null, "priority": { "self": "https://test.atlassian.net/rest/api/2/priority/3", "iconUrl": "https://test.atlassian.net/images/icons/priorities/medium.svg", "name": "Medium", "id": "3" }, "customfield_10023": [], "customfield_10024": null, "customfield_10025": null, "labels": [], "customfield_10026": null, "customfield_10016": null, "customfield_10017": null, "customfield_10018": null, "customfield_10019": null, "timeestimate": null, "aggregatetimeoriginalestimate": null, "versions": [], "issuelinks": [], "assignee": null, "updated": "2016-06-27T16:05:02.852+0300", "status": { "self": "https://test.atlassian.net/rest/api/2/status/10001", "description": "This was auto-generated by JIRA Service Desk during workflow import", "iconUrl": "https://test.atlassian.net/images/icons/status_generic.gif", "name": "Waiting for support", "id": "10001", "statusCategory": { "self": "https://test.atlassian.net/rest/api/2/statuscategory/1", "id": 1, "key": "undefined", "colorName": "medium-gray", "name": "No Category" } }, "components": [], "timeoriginalestimate": null, "description": "test description", "customfield_10010": null, "customfield_10011": null, "customfield_10012": null, "customfield_10013": null, "customfield_10014": null, "timetracking": {}, "customfield_10015": null, "customfield_10007": "0|i0009b:", "customfield_10008": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@cf82e6", "attachment": [], "customfield_10009": null, "aggregatetimeestimate": null, "summary": "New Summary", "creator": { "self": "https://test.atlassian.net/rest/api/2/user?username=admin", "name": "admin", "key": "admin", "emailAddress": "email@emailserver.tld", "avatarUrls": { "48x48": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=48", "24x24": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=24", "16x16": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=16", "32x32": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=32" }, "displayName": "Administrator", "active": true, "timeZone": "Europe/Helsinki" }, "subtasks": [], "reporter": { "self": "https://test.atlassian.net/rest/api/2/user?username=admin", "name": "admin", "key": "admin", "emailAddress": "email@emailserver.tld", "avatarUrls": { "48x48": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=48", "24x24": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=24", "16x16": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=16", "32x32": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=32" }, "displayName": "Administrator", "active": true, "timeZone": "Europe/Helsinki" }, "customfield_10000": null, "aggregateprogress": { "progress": 0, "total": 0 }, "customfield_10001": null, "customfield_10002": null, "customfield_10003": null, "environment": null, "duedate": null, "progress": { "progress": 0, "total": 0 }, "comment": { "comments": [ { "self": "https://test.atlassian.net/rest/api/2/issue/10042/comment/10027", "id": "10027", "author": { "self": "https://test.atlassian.net/rest/api/2/user?username=admin", "name": "admin", "key": "admin", "emailAddress": "email@emailserver.tld", "avatarUrls": { "48x48": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=48", "24x24": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=24", "16x16": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=16", "32x32": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=32" }, "displayName": "Administrator", "active": true, "timeZone": "Europe/Helsinki" }, "body": "test comment", "updateAuthor": { "self": "https://test.atlassian.net/rest/api/2/user?username=admin", "name": "admin", "key": "admin", "emailAddress": "email@emailserver.tld", "avatarUrls": { "48x48": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=48", "24x24": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=24", "16x16": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=16", "32x32": "https://secure.gravatar.com/avatar/asd0a6bb5e5c8ce4c5152b54b45ee5c?d=mm&s=32" }, "displayName": "Administrator", "active": true, "timeZone": "Europe/Helsinki" }, "created": 1467032702852, "updated": 1467032702852 } ], "maxResults": 1, "total": 1, "startAt": 0 }, "votes": { "self": "https://test.atlassian.net/rest/api/2/issue/TEST-43/votes", "votes": 0, "hasVoted": false }, "worklog": { "startAt": 0, "maxResults": 20, "total": 0 } } }, "timestamp": 1467032703044}

Integration via OEC (for On Premise Jira Service Management Usage)

Jira Service Desk is now Jira Service Management!The product name may have changed, but we'll continue using the old name (Jira Service Desk) in the scripts until the next update.

Use Opsgenie's OEC and the Jira ServiceDesk script to update requests on Jira Service Management. This enables the deployment of your own scripts/ability to modify the ones provided and execute customized actions on Jira Service Management.

To use the Jira ServiceDesk integration package, follow the steps in the sections below through the end.

Download the latest version of OEC

To download the latest version ofJiraServiceDeskpackage, please usereadme file of oec-scripts repository.

Installation

For Red Hat Based Distributions

  • Run following command :rpm -i opsgenie-jiraservicedesk-<your_version>.rpm

For Debian Based Distributions

  • Run following command :dpkg -i opsgenie-jiraservicedesk-<your_version>.deb

    (Video) Start to Finish Incident Management with Jira Service Management and Opsgenie

For Windows

  • Unzip opsgenie jiraservicedesk zip file which contains OEC package into a directory (C:\opsgenie is the preferred path.) Follow the instructionshereto install OEC on Windows.

  • In order to learn more about how to run OEC you can refer to theRunning OEC documentation.

Configuring Jira Service Management Integration for OEC

  • In order to use OEC utility,enable Send Via OEC.

  • Other configurations regarding Jira Service Management can be done either via integration page or OEC configuration fileconfig.json. The configuration via the integration page precedes the configuration file.

Integrate Opsgenie with Jira Service Management | Opsgenie | Atlassian Support (6)

OEC Configuration

To be able to execute actions in Jira Software, OEC gets the configuration parameters from the configuration file located at path /home/opsgenie/oec/conf/config.json.

Configuration parameters

  • apiKey – Copy the API key from the Jira integration you've created above.

  • issueTypeName – Type of the issue which can be "Task", "Bug", "Story" or your custom issue type ("Epic" is not supported).

  • url – Your Jira Service Management url where issues will be created, resolved, closed etc.

  • username – Your username for your Jira Service Management account.

  • password – Your password for your Jira Service Management account.

  • key – The issues will be created for this project.

The package that you downloaded also includes OEC utility which is located under /usr/local/bin and the script that is needed to be run by OEC which is under /home/opsgenie/oec/scripts. After the configuration of OEC is done, you need to run it. In order to learn more about how to run OEC, you can refer to theRunning OEC documentation.

Sample parameters sent to OEC

JSON

12345678910111213141516171819{ "summary":"test", "issueTypeName":"Task", "integrationName":"Jira Service Management", "sendViaOEC":true, "description":"this is a test", "integrationId":"3af28c92-b71c-459c-8d72-04a6f7f7ebac", "url":"https://jiratestopsgenie.atlassian.net", "password":"******", "projectKey":"OPSGENIE", "integrationType":"JiraServiceDesk", "customerId":"04912a27-5fc1-4145-a6dd-8819afc0d870", "alias":"c570a4cc-3f57-4b60-814e-f04c63e7442d", "action":"Create", "alertId":"c570a4cc-3f57-4b60-814e-f04c63e7442d", "key":null, "mappedAction":"createIssue", "username":"jiratest@opsgenie.com"}

Troubleshooting

  1. If amandatory custom fieldis set for creating an issue in Jira Service Management, a Jira Service Management issue cannot be created from an Opsgenie alert. However, by using OEC and configuring the script, the creation of Jira request can be achieved.

  2. If a comment cannot be added to an issue by performing an action on an alert, please look at theLogspage first. If the URL does not contain the issue key it means there is no issue in Jira ServiceManagement populated from that alert. Thus it could not add a comment to a non-existing issue.

  3. Opsgenie's Jira Service Management integration allows setting the status of the issue toRESOLVEDin Jira Service Management. However, if the workflow of the project doesnotallow that transitions, youcannotset that transition using Opsgenie too.

  4. Jira Service Management does not support non-ASCII characters. Having non-ASCII characters on payload to be sent to Jira Service Management may cause 400 Bad Request Error.

  5. If the Jira Service Management integration is assigned to a team, in order to create issues in Jira Service Management from alerts created in Opsgenie, the other integrations must also be assigned to the same team, or, no team must be assigned for both the Jira Service Management integration and the other Opsgenie integrations.

  6. If you receive a Reason: 400 Bad Request error in the activity logs after attempting to create a Jira Service Management request from an Opsgenie alert, check the Logs page for detailed information on this response. An example pf the error you may see in the Logs page is: "labels":"Field 'labels' cannot be set. It is not on the appropriate screen, or unknown". To resolve this go to your Jira Service Management account and add the missing field from project settings.

    (Video) Modern incident management with Opsgenie and Jira Service Management | Team '22 | Atlassian

FAQs

What is Opsgenie used for? ›

Opsgenie is a modern incident management platform that ensures critical incidents are never missed, and actions are taken by the right people in the shortest possible time. Opsgenie receives alerts from your monitoring systems and custom applications and categorizes each alert based on importance and timing.

Can Jira be used for incident management? ›

Atlassian's platform for incident management brings all of the context and data you need to resolve an incident quickly and efficiently. Within Jira Service Management, agents can easily manage issues and user-reported incidents. Agents can quickly escalate major incidents as an alert to the on-call team.

Is Opsgenie part of Jira service management? ›

As a customer of both Jira Service Management and Opsgenie, you have some options. You can continue to use Opsgenie separately, or have your entire team use Jira Service Management that includes Opsgenie functionality. On one platform, you can move faster and benefit from unified license management.

What are the 5 stages of the incident management process? ›

6 Steps to Incident Management
  • Incident Detection. You need to be able to detect an incident even before the customer spots it. ...
  • Prioritization and Support. ...
  • Investigation and Diagnosis. ...
  • Resolution. ...
  • Incident Closure.

How do I create an incident in Jira service management? ›

Create an incident
  1. Create an issue in your project, and set its type to Incident.
  2. Write a summary. Let's say "I can't send emails".
  3. Set the Affected Business Service field to Email service. What you're doing here is actually choosing the affected Insight object.
2 Feb 2021

What is incident management interview questions and answers? ›

Interview Questions for Incident Managers:
  • How would you go about leading an incident investigation? ...
  • How would you manage a large team of technical staff? ...
  • How do you keep up to date with the changing IT industry and new software programs? ...
  • Which incident management software systems do you enjoy working with?

Does atlassian own OpsGenie? ›

OpsGenie is an IT incident management software that was bought by Atlassian for $295M at around a 20x revenue multiple.

How do you pronounce OpsGenie? ›

What is Opsgenie? - YouTube

What is Jira access? ›

How it works. Atlassian Access is an organization-wide subscription that connects your Atlassian cloud products to your identity provider. It allows you to enable enterprise-grade authentication features, and additional oversight, across your company domains.

What are 3 types of incidents? ›

3 Types of Incidents You Must Be Prepared to Deal With
  • Major Incidents. Large-scale incidents may not come up too often, but when they do hit, organizations need to be prepared to deal with them quickly and efficiently. ...
  • Repetitive Incidents. ...
  • Complex Incidents.
16 Dec 2015

What are the 7 steps in incident response? ›

In the event of a cybersecurity incident, best practice incident response guidelines follow a well-established seven step process: Prepare; Identify; Contain; Eradicate; Restore; Learn; Test and Repeat: Preparation matters: The key word in an incident plan is not 'incident'; preparation is everything.

What is incident management roles and responsibilities? ›

An incident manager's job is to respond to incidents when they occur and take any necessary steps to restore service and return the business to normal operations as quickly as possible. Incident managers are the IT staff members with which employees, suppliers, and customers interact when they are stuck and need help.

What is ITIL incident management? ›

ITIL incident management (IM) is the practice of restoring services as quickly as possible after an incident. And it's a main component of ITIL service support. ITIL incident management is a reactive process. You can use IM to diagnose and escalate procedures to restore service. So, it's not a proactive measure.

What is Jira issue type? ›

Issue types distinguish different types of work in unique ways, and help you identify, categorize, and report on your team's work across your Jira site. They can help your team build more structure into your working process.

What is the difference between incident and service request? ›

Incident: Restoring something that is broken/disrupted. Examples include fixing a printer, phone, or software. Service Request: Fulfilling a request for information/advice or access a Service. Examples include resetting a password, granting access to a printer, or providing standard setup Services for a new employee.

What is new Opsgenie? ›

Opsgenie is a relatively new Atlassian product. It proactively helps Operations (Ops) teams manage incidents. This solution encourages collaboration between all the other teams and Ops based on automated functionalities.

How do you pronounce Opsgenie? ›

What is Opsgenie? - YouTube

Does atlassian own Opsgenie? ›

OpsGenie is an IT incident management software that was bought by Atlassian for $295M at around a 20x revenue multiple.

How do I log into Opsgenie? ›

  1. Go to app.opsgenie.com and enter your user credentials, or.
  2. Log in directly to one of your Atlassian Cloud products and use the app switcher to go to Opsgenie.

What is heartbeat in Opsgenie? ›

Our Heartbeats feature can be used to ensure that your environment is able to connect to Opsgenie continuously and that: There are no network problems between your system and Opsgenie. Your Heartbeat sender system is working as expected.

Does Opsgenie have an API? ›

What does Opsgenie offer API integration users? API Integrations are used to access Opsgenie services, allowing you to integrate alerts, configure users, schedules, and teams on your Opsgenie account from external applications.

How do I send an alert on Opsgenie? ›

Basic configuration to create alerts

Log in to your Opsgenie account. Go to Settings > Integrations and search for Email. Each email integration is assigned a customizable email address. Specify who is notified of Email alerts using the Responders field.

Videos

1. Getting the Most out of Atlassian and Opsgenie
(Opsgenie)
2. What's new in Opsgenie, Statuspage, Jira Service Desk
(Atlassian)
3. Webinar: Automate Actions During Incidents Using Opsgenie
(Opsgenie)
4. Jira Service Management: Incident Management Tour
(Opsgenie)
5. Jira Service Management Demo & Discussion | Trundl
(Trundl Inc)
6. Getting Started in Opsgenie
(Opsgenie)

Top Articles

You might also like

Latest Posts

Article information

Author: Corie Satterfield

Last Updated: 09/28/2022

Views: 5549

Rating: 4.1 / 5 (42 voted)

Reviews: 81% of readers found this page helpful

Author information

Name: Corie Satterfield

Birthday: 1992-08-19

Address: 850 Benjamin Bridge, Dickinsonchester, CO 68572-0542

Phone: +26813599986666

Job: Sales Manager

Hobby: Table tennis, Soapmaking, Flower arranging, amateur radio, Rock climbing, scrapbook, Horseback riding

Introduction: My name is Corie Satterfield, I am a fancy, perfect, spotless, quaint, fantastic, funny, lucky person who loves writing and wants to share my knowledge and understanding with you.