Create Integration Profile
Overview
The Integration module in Motadata AIOps facilitates seamless integration of various supported services with Motadata AIOps. This empowers users to harness the capabilities of AIOps and automate tasks such as incident creation based on Alerts generated in Motadata AIOps.
Integration capability not only enhances user convenience but also significantly reduces the potentiality of errors. Motadata AIOps supports integration with a variety of services:
- Motadata ServiceOps
- ServiceNow
- Microsoft Teams
- Atlassian JIRA
Integration Profile Screen
On this screen you will be able to view all the configured Integration Profile for all the integration types. Following are all the option available on the screen:
| Field | Description |
|---|---|
| Profile Name | Name of the Integration profile. |
| Description | Description of the Integration profile. |
| Integration Type | Type of the integration selected for the profile. |
| Used Count | Number of times the profile is mapped with an alert. |
| Action | Actions available for the Integration profile; will be discussed in detail further in the guide. |
To create a new Integration Profile, click on the Create Integration Profile button.
Since each Integration Profile requires you to configure different parameters, we have listed each one separately for ease of convenience.
- ServiceOps
- ServiceNow
- Microsoft Teams
- Atlassian JIRA
Motadata ServiceOps Integration
Overview
The ServiceOps Integration module in Motadata AIOps facilitates seamless integration with Motadata ServiceOps, an IT Service Management (ITSM) tool. This integration empowers users to create incidents in ServiceOps automatically when specific alerts with predefined severities are triggered in Motadata AIOps. By streamlining incident management processes, organizations can enhance their response efficiency and ensure timely resolution of critical issues.
Prerequisites
Before you can proceed with creating an Integration Profile, you will need to ensure you have configured Motadata AIOps to ServiceOps Integration.
Navigation
Go to Menu. Select Settings 
. After that, Go to Integration 
and select Motadata ServiceOps. The Motadata ServiceOps integration screen is displayed.
Integration Profile Parameters
Ensure that the necessary prerequisites are met, including the creation of the integration in ServiceOps and obtaining the related Client ID and Client Secret, before proceeding with the integration configuration.
To configure the integration with Motadata ServiceOps, enter the following details on the ServiceOps integration screen:
| Field | Description |
|---|---|
| Profile Name | Provide a profile name for the integration profile. |
| Integration Type | Select Service Ops from the dropdown menu. |
| Description | Enter a description for the integration profile, if required. |
| Category | Select a category from the dropdown menu. |
| Sub-Category | Select a sub-category from the dropdown menu. |
| Group | Select a Group from the dropdown menu. The list of Group will be imported as is from ServiceNow. |
| Technician | Technician will be auto-selected based on the group. You can request a specific technician from the dropdown menu. |
| Impact | Select Impact severity for the alert from the dropdown. |
| Urgency | Select an urgency timeline for the alert from the dropdown. |
| Service | Choose a service from the dropdown. |
| Service Offering | Select a service offering based on the option you chose in the Service field. |
| Delay Trigger | Enter a numerical value to delay the ticket generation on ServiceNow. The value is in minutes. |
| Business Hour | Use the dropdown to select business hour timings. ServiceNow will only generate tickets during the specified business hours. |
| Do not trigger if the alert is Acknowledged | This option is only available when Delay Trigger option is active. If the alert is acknowledged, no incident will be created on ServiceNow. |
| Auto Close Ticket | Toggle this button to automatically close the ticket in ServiceOps when the corresponding alert moves to a clear severity state in AIOps. |
| Ticket Status | This option is only available when Auto Close Ticket is enabled. You can choose if you want to show the status of cleared tickets as Closed or Resolved upon Auto-Close. |
Select the Reset button to erase all the current field values, if required.
Select the Test button to test the integration configuration.
Select the Save button to save the integrations configuration.
ServiceNow Integration
Overview
Integration Profile will facilitate raising an incident based on the alert generated on the Motadata AIOps. You can map multiple fields, for instance Group, Technician, Category, Service, Impact, and Urgency right from the Integration Profile screen.
Prerequisites
Before you can proceed with creating an Integration Profile, you will need to ensure you have configured Motadata AIOps to ServiceNow Integration.
Navigation
Go to Menu. Select Settings . After that, Go to Integration and select ServiceNow. The Motadata ServiceNow integration screen is displayed.
Integration Profile Parameters
You will need to configure integration profile parameters on Motadata AIOps in order to properly create Incidents/Events on ServiceNow. Enter the following details on the Create Integration Profile page:
| Field | Description |
|---|---|
| Profile Name | Provide a profile name for the integration profile. |
| Integration Type | Select Service Now from the dropdown menu. |
| Description | Enter a description for the integration profile, if required. |
| Category | Select a category from the dropdown menu. |
| Sub-Category | Select a sub-category from the dropdown menu. |
| Group | Select a Group from the dropdown menu. The list of Group will be imported as is from ServiceNow. |
| Technician | Technician will be auto-selected based on the group. You can request a specific technician from the dropdown menu. |
| Impact | Select Impact severity for the alert from the dropdown. |
| Urgency | Select an urgency timeline for the alert from the dropdown. |
| Assignee | Select an assignee for the ticket from the dropdown. |
| Department | Select the department of the assignee from the dropdown. |
| Delay Trigger | Enter a numerical value to delay the ticket generation on ServiceNow. The value is in minutes. |
| Business Hour | Use the dropdown to select business hour timings. ServiceNow will only generate tickets during the specified business hours. |
| Do not trigger if the alert is Acknowledged | This option is only available when Delay Trigger option is active. If the alert is acknowledged, no incident will be created on ServiceNow. |
| Auto Close Ticket | Toggle this button to automatically close the ticket in ServiceNow when the corresponding alert moves to a clear severity state in AIOps. |
| Ticket Status | This option is only available when Auto Close Ticket is enabled. You can choose if you want to show the status of cleared tickets as Closed or Resolved upon Auto-Close. |
Select the Reset button to erase all the current field values, if required.
Select the Create Integration Profile button to create the profile.
Microsoft Teams Integration
Overview
The Microsoft Teams integration allows seamless communication between Motadata AIOps and your internal IT teams. By connecting your Teams channels, you can receive critical alerts and notifications directly within your familiar collaboration environment. This ensures timely awareness of any significant events or issues related to your network infrastructure.
The integration provides granular control, enabling you to specify which Teams channels receive notifications for specific events or alerts. This targeted delivery of information empowers your team to make informed decisions and respond promptly to any critical situations.
Prerequisites
Before you can proceed with creating an Integration Profile, you will need to ensure you have configured Motadata AIOps to Microsoft Teams Integration.
Navigation
Go to Menu. Select Settings . After that, Go to Integration and select Microsoft Teams. The Microsoft Teams integration screen is displayed.
Integration Profile Parameters
You will need to configure integration profile parameters on Motadata AIOps in order to ensure intimation is sent to defined channel on Microsoft Teams. Enter the following details on the Create Integration Profile page:
| Field | Description |
|---|---|
| Profile Name | Provide a profile name for the integration profile. |
| Integration Type | Select Microsoft Teams from the dropdown menu. |
| Description | Enter a description for the integration profile, if required. |
| Handle Name | Provide a handle name. This handle name will be used in Policy settings to intimate people/channel you assign to this particular handle. |
| Team | Select a Team from the dropdown menu. |
| Channel Type | Choose the channel type from Public or Private |
| Channel | Use the dropdown to select a channel which would be intimated when a policy is breached. |
Click on the Test button to perform a test run of the configuration. For testing, Motadata AIOps will send a message to the Microsoft Teams channel you configured in the profile.
Select the Reset button to erase all the current field values, if required.
Select the Create Integration Profile button to create the profile.
Atlassian JIRA
Overview
The integration of Motadata AIOps with Atlassian JIRA bridges the gap between network operations and incident management workflows. This integration enhances operational efficiency by automating the creation of JIRA issues directly from Motadata AIOps alerts.
The integration establishes a synchronization of updates between Motadata AIOps and Atlassian JIRA. This ensures data consistency across both platforms, affording a unified and current perspective on incident resolution progress.This streamlines incident management, improves team collaboration, and ultimately contributes to faster mean time to resolution (MTTR).
Prerequisites
Before you can proceed with creating an Integration Profile, you will need to ensure you have configured Motadata AIOps to Atlassian JIRA Integration.
JIRA Workflow Mapping
The integration does not override JIRA's workflow rules. It must respect the workflow design configured in JIRA. Hence, JIRA issues can only change states as defined by the workflow rules of your project.
For instance, if an issue is in the 'In Progress' state, it cannot be directly closed unless the workflow explicitly allows a state change from 'In Progress' to 'Closed'.
If the integration attempts to perform an invalid state change (e.g., closing a ticket from an incompatible state), the action will fail.
Similarly, reopening a ticket may require specific state change (e.g., from 'Closed' to 'Reopened') that must be defined in the workflow.
Status and Transition Matching
The current integration relies on exact naming matches between the statuses and transitions in JIRA.
If the integration is set to auto-close a ticket, the transition name (e.g., 'Close') must exactly match the status available in the JIRA workflow for that ticket's current state. Along with that, your project workflow should also allow the direct status change as mentioned in the previous section.
If the names do not match, (for instance, transition is 'Close' and status is 'Resolve'), the auto-close functionality will fail.
To understand statuses and transitions better, refer to the image below:
As you can view in the image, the transitions on the left side match exactly with the statuses on the right side. Ensure your project workflow follows the same methodology to ensure auto-close and reopen ticket feature functions as expected.
Navigation
Go to Menu. Select Settings . After that, Go to Integration and select Atlassian JIRA. The Atlassian JIRA integration screen is displayed.
Integration Profile Parameters
You will need to configure integration profile parameters on Motadata AIOps in order to properly create Incidents/Tasks/Bugs on JIRA. Enter the following details on the Create Integration Profile page:
| Field | Description |
|---|---|
| Profile Name | Provide a profile name for the integration profile. |
| Integration Type | Select Atlassian JIRA from the dropdown menu. |
| Description | Enter a description for the integration profile, if required. |
| Project | Select the project using the dropdown for which you want to create the integration profile. |
| Issue Type | Select an issue type to create using the dropdown. (Every issue type has different configuration parameters). |
| Component(s) | Select a component of the JIRA project using the dropdown menu. |
| Reporter | Choose a reporter using the dropdown menu. |
| Assignee | Choose an assignee using the dropdown menu. |
| Priority | Select a priority for the issue/task/incident using the dropdown. |
| Labels | Enter a label name you wish to assign. |
| Auto Close Ticket | Toggle this button to automatically close the ticket in JIRA when the corresponding alert moves to a clear severity state in AIOps. |
| Issue Status | This option is only available when Auto Close Ticket is enabled. You can choose the status you want to display for auto-closed tickets using the dropdown. |
| Re-open closed ticket | This option is only available when Reopen closed ticket is enabled for the integration. Use the dropdown to select the status of the issue if and when it is reopened. |
Make sure you only populate the field(s) in the Integration profile that are present in your JIRA project. For instance, if your JIRA project does not have a 'Label' field and you populate the 'Label' field in the integration profile, the issue/task/incident creation will fail.
Ensure you have deployed required workflows in order to auto close tickets on Atlassian JIRA. You can read more on required JIRA workflows in the Prerequisites section of this guide.
Select the Reset button to erase all the current field values and start afresh.
Select the Create Integration Profile button to create the profile.