Integrate with N-ABLE N‑central RMM

This article highlights a new alerting feature that's natively available in Jira Service Management which is gradually rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.

What does the integration offer?

Use the N-ABLE N‑central RMM integration to send N‑central RMM issues to Jira Service Management with detailed information. Jira Service Management acts as a dispatcher for N-ABLE N‑central RMM alerts, determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls, iOS & Android push notifications, and escalates alerts until they are acknowledged or closed.

How does the integration work?

When an issue is created in N-ABLE N‑central RMM, an alert is created in Jira Service Management automatically through the integration.
When the issue's state turned back to Normal in N-ABLE N‑central RMM, the related alert is closed in Jira Service Management automatically.
When the issue is acknowledged in N-ABLE N‑central RMM, the related alert is acknowledged in Jira Service Management automatically.

Set up the integration

N-ABLE N‑central RMM is a bidirectional integration. Setting it up involves the following steps:

Add an N-ABLE N‑central RMM integration in Jira Service Management
Configure the integration in N-ABLE N‑central RMM

Add an N-ABLE N‑central RMM integration

Bidirectional integrations aren’t supported in Free and Standard plans. All the other integrations are supported at a team level in Free and Standard; however, for their outgoing part to work, you need to upgrade to a higher plan. To add any integration at a site level through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be either on Premium or Enterprise.

Adding an integration from your team’s operations page makes your team the owner of the integration. This means Jira Service Management only assigns the alerts received through this integration to your team.

To add an N‑central RMM integration in Jira Service Management, complete the following steps:

Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “N-ABLE N‑central RMM”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
Select Continue.
The integration is saved at this point.
Expand the Steps to configure the integration section and copy the API URL.
You will use this URL while configuring the integration in N-ABLE N‑central RMM later.
Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.

Configure the integration in N-ABLE N‑central RMM

To configure the integration in N-ABLE N‑central RMM, complete the following steps:

In N‑central RMM, select the user icon at the top to go to the Modify User page.
Select User Details.
Select Notification Method.
Select ADD.
Select Third Party Integration - HTTP for the notification method.
Paste the URL previously copied from Jira Service Management into Target URL.
Select Save.

Integrate via JEC

Use Jira Service Management’s JEC and the N‑central RMM script to update alerts on N‑central RMM. With this setup, you can deploy your own script, modify the ones provided, or run customized actions on N-central RMM. To use the N‑central RMM integration package, complete the following steps:

Download the latest version of JEC for the N‑central RMM package.
Install the package.

For Windows

Unzip Jira Service Management integration zip file which contains the JEC package into a directory (C:\jsm\jec is the preferred path). Read more about installing JEC on Windows.

To execute actions in N-ABLE N‑central RMM, JEC gets the configuration parameters from the configuration file (found under the directory where the zip file is extracted). If you used the preferred path in Windows, it is C:\jsm\jec\config.json.

Configure N-ABLE N‑central RMM integration for JEC

To execute actions in N-ABLE N‑central RMM, JEC gets the configuration parameters from the configuration file. Read more about running JEC.

Configuration parameters

Parameter	Description	Mandatory?
apiKey	Paste the API key you copied while creating the N-ABLE N‑central RMM integration in Jira Service Management	Yes
username	Your N-ABLE N‑central RMM username	No
password	Your N-ABLE N‑central RMM password	No
url	N-ABLE N‑central RMM URL	No

Sample parameters sent to JEC

(in JSON format)

{
   "type":"nablencentral",
   "alertId":"0e321daf-6532-4277-a61c-83d90dea9969",
   "customerId":"d17aae0e-7730-4788-bbd5-a306816287d3",
   "action":"Acknowledge",
   "mappedActionV2":
    {
      "name":"acknowledgeNotification",
      "extraField":""
    },
    "integrationId":"2bdcf8c9-a423-4efd-957c-07ee7de236ea",
    "integrationName":"AppMon",
    "integrationType":"AppMon",
    "sendViaJEC":true,
    "activeNotificationTriggerId":"",
    "userName":"",
    "password":"",
    "url":"",
    "alias":"b324f7e2-c747-47bb-83d5-17b6a8eafaf8"
}

Was this helpful?

It wasn't accurate

It wasn't clear

It wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community