This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.

Skip to end of metadata
Go to start of metadata

(New in 4.3.3) The AppDynamics with Atlassian JIRA Integration is a two-way integration system that can automatically create and update JIRA tickets when Incidents occur.

You can use a JIRA Ticket widget in War Rooms and Custom Dashboards to view detailed ticket information directly in AppDynamics. You can also view JIRA ticket information, such as status, assignee, and priority directly from the Health Rule Violations table.

Atlassian JIRA Integration Runtime Flow

The Integration helps reduce the time in searching for specific event/incident data and consolidate tickets by following this runtime flow:

  1. AppDynamics event triggers a JIRA Incident. The event is a health rule violation.
  2. AppDynamics event and incident data is gathered in a JIRA issue.
  3. AppDynamics War Room is used to facilitate the resolution. You can place a JIRA widget to track the progress of issues in real-time. See Virtual War Room.
  4. The war room is archived into JIRA upon the end of the WarRoom or if you choose to archive at any given point in time. See Virtual War Room.

The information gathered in the JIRA issue and war room persists between AppDynamics and JIRA, and can help you conduct a proper root cause analysis (RCA). You can navigate between the AppDynamics and JIRA interfaces for a continuous experience.

Configure Atlassian JIRA Integration

You can configure the Atlassian JIRA Integration by using open authentication (OAuth). The OAuth model passes back and forth the consumer and public keys, and creates links on the Atlassian system. This is done through a wizard, where you type in the URL, create the public keys, and launch the Atlassian links you need. Once this is set up, you do not have to worry about authorization linked to the JIRA system. OAuth requires JIRA administrator access.

For OAuth:

  1. Log in to the Controller UI as an administrator. 
  2. Click Settings > Administration.
  3. In the Administration window, click the Integration tab and then Atlassian JIRA OAuth from the Integrations list.

  4. Click Start JIRA Integration Wizard

  5. Follow the wizard steps:

    1. Enter your JIRA host URL.

      The Controller makes REST API calls to the JIRA instance via regular HTTP/HTTPS ports. Therefore, as long as the Controller host can reach the JIRA instance host over this URL, then the integration will work.

    2. Create an Application Link in JIRA.

    3. Authorize AppDynamics in JIRA. 

  6. Click Save.

Create a JIRA Issue with the Integration

You can define policies that, when triggered, generate JIRA issues. See JIRA Actions for more details. Flexible information such as event reason, error stack, etc. is inserted based on the event type and can be defined on an action-by-action basis. 

To create a JIRA from configured health rules:

  1. Follow the steps on JIRA Actions to create a JIRA action.
  2. Go back to the Alert & Respond main page, and create a Health Rule. See Configure Health Rules.
  3. Go back to the Alert & Respond main page, and create a Policy. See Configure Policies.
    1. Make the policy trigger based on the Health Rule Violation Events.
    2. Make the policy execute the JIRA action you created earlier.

Start and Manage a War Room with the Integration

You can collaborate with other users leveraging the AppDynamics War Room feature with the Atlassian JIRA integration. The integration makes it easy for you to track all content related to an AppDynamics war room incident. See Virtual War Room for more details on how to start a war room.

Issue Tracking Widget

If you're the owner of the war room, you can set up the JIRA integration for the room by adding an Issue Tracking Widget. To add the widget, click the + icon, then click the Issue Tracking widget icon under Other Widgets.

After you configure a widget, it can display the JIRA issue's:

  • Title and description
  • Status
  • Assignee
  • Target version
  • Complete timeline of changes, with the respective information about who made the change as well as the change delta showing previous and new values of the changed fields

As the ticket's information is updated on the remote system, this information is propagated into the War Room for all users to see. Updates are not limited to any particular information field and should cover all tracked fields. All users should see the same information at any given point in time with the latest ticket status as well as all the previous activity on the ticket. However, the interaction with the widget is different depending on the user type:

  • War Room Owner
    For the owner of the War Room, the widget will display the options to modify the widget properties. Widget properties include every option which can be customized for any generic widget, as well as the option to change the ticket(s) being tracked. Upon changing of the properties, all the viewers of the war room will see the updates propagate without the need to refresh the War Room. This update also includes all the changes to the ticket(s) being tracked.
  • War Room Viewer
    For the user viewing the widget, they'll be able to see the updates to the JIRA ticket tracker setup by the War Room owner. Regular War Room users will not be able to view the widget properties or edit the JIRA tracker widget.
  • Shared War Room Viewer
    Shared War Rooms are unique in that they are able to be viewed without the explicit sign in required into the AppDynamics product. For this purpose, we display the most current information inside the JIRA widget as we would for regular war room viewers. This allows outside teams and executive stakeholders to monitor the status of the issue resolution.

See Virtual War Room for more details on the widget.

Navigating Through the Atlassian JIRA Integration

When you are conducting an RCA on a specific incident or event, you have to review numerous tickets to correlate the RCA, however the data for AppDynamics is in many different locations within the application. This integration consolidates JIRA information related to an AppDynamics Incident and Event, and also provides you with a central location to conduct an RCA with all the relevant data in one location. The navigation setup of the Atlassian JIRA integration reduces time in searching for specific event and incident data.

JIRA Integration Health Rule Violations Table Column

With the integration enabled, you are able to view a new column in the Health Rule Violations table found on the Health Rule Violations page.

You can leverage this column to view basic details on the related JIRA issue. You can also click on the JIRA Key to see the JIRA issue itself. In addition, you can start or join a war room.

War Room Issue Tracking Details

The Issue Tracking widget in the war room allows you to see live updates of the related JIRA issue. Click on the issue title to jump to the JIRA issue page.

Archive a War Room

You can save the war room as a JIRA attachment for later use and analysis by selecting Archive War Room under Actions. The archival process gives you the option to select a ticket to archive the war room into, but by default, it selects the JIRA that is correlated with the Incident. The war room attachment consists of a screenshot of the war room at that point in time, without the navigation interface. See Virtual War Room.

Disabling the Atlassian JIRA Integration

You can disable your Atlassian JIRA Integration to disable all JIRA functionality. The Atlassian JIRA Integration features in the AppDynamics UI are disabled by default.

Disabling the integration from the administration settings will disable the following features:

  • JIRA action
  • Issue Tracking widget
  • JIRA / War Room column in the Health Rule Violations table

Disabling these features does not delete them. So reenabling the integration will also reenable the features, and restore their original views.

Watch the Video

 For full-screen viewing, click AppDynamics iQ Integration with Atlassian JIRA.

  • No labels