Automatically create issues in an on-premise Jira instance when Cloudmon alarms fire, and optionally resolve them when the alarm clears.
The Jira ServiceDesk (On-Premise) integration allows Cloudmon to create issues in a project on your self-hosted Jira Server or Data Center instance when an alarm fires. It is intended for teams that cannot use Jira Cloud. If automatic resolution is enabled, Cloudmon also moves the issue to its resolved status when the alarm clears.
Collect the following details in Jira before you configure the integration in Cloudmon.
| Field | Description |
| Site URL | The address your team uses to sign in to this Jira instance, including the port if it is not the default, for example http://jira.acme.local:8080. |
| Username / Password | A Jira account that can create and edit issues in the target project. See Create, edit, or remove a user. |
| Project Key | The short key of the target project. See Editing a project key. |
| Issue Type | One of the types configured for that project, for example Task or Incident. See Defining issue type field values. |
| Resolution Transition | The workflow transition that moves an issue to its resolved or done status. See Working with workflows. |
The password is stored encrypted and is never shown again after saving. Use Test Connection to verify the site, account and project before saving.
Jira Account
| Field | Description |
| Integration Name | A display name to identify this integration in Cloudmon, such as "Ops Jira". |
| Site URL | The address of your Jira instance, including the port if it is not the default, for example http://jira.acme.local:8080. |
| Username | The Jira account Cloudmon uses to create issues. |
| Password | The password of the Jira account. |
| Verify SSL Certificate | Selected by default. When selected, Cloudmon verifies the SSL certificate of the Jira instance. |
| Project Key | Enter the Site URL and the account credentials first, then click Fetch Projects. Then select the project from the dropdown. |
| Issue Type | Select a project first, then select an issue type from the dropdown. Use the Refresh button to reload the issue types for the selected project. |
| Resolution Transition | The name of the workflow transition that moves the issue to its resolved status. The default is Resolve. |
Ticket Settings
| Field | Description |
| Ticket Subject | The text used as the Jira issue subject. The default is $device_name is $severity - $title. Type $ to pick a replaceable tag from the list, and use the reset icon beside the field to restore the default. |
| Create Tickets For Severities | Select the alarm severities that create a Jira issue: Down, Critical, Trouble and Attention. At least one must be selected. |
| Resolve Ticket Automatically When Alarm Clears | Enabled by default. When enabled, Cloudmon resolves the Jira issue when the alarm clears. When disabled, the Jira issue must be resolved manually. |
| Ticket Tags | Optional. Type a tag and press Enter to add it. Add as many as you need. |
The Reset button restores the form to its default values, and Close exits without saving.
When this alarm fires, Cloudmon creates an issue in Jira automatically, for the severities selected in the integration.