Automatically raise incidents in Freshservice when Cloudmon alarms fire, and manage them through your ITSM workflow.
The Freshservice integration allows Cloudmon to raise tickets in your Freshservice account when an alarm fires. If automatic resolution is enabled, Cloudmon also resolves the ticket when the alarm clears, keeping Freshservice in step with your monitoring state without manual intervention.
Collect the following details in Freshservice before you configure the integration in Cloudmon.
| Field | Description |
| Domain | Your Freshservice host from the browser address bar, for example https://acme.freshservice.com. |
| API Key | Found in your Freshservice Profile Settings. See Where do I find my API key?. |
| Requester Email | An existing Freshservice requester, or leave it for Freshservice to create. See Adding requesters into your service desk. |
| Agent permission | The agent behind the API key needs a role that can create and edit tickets. See Manage agent roles and permissions in your Service Desk. |
| Ticket Tags | Free text. Any tag entered in Cloudmon is created in Freshservice on first use. See Tagging. |
The API key is stored encrypted and is never shown again after saving. Use Test Connection to verify the domain and key before saving.
Freshservice Account
| Field | Description |
| Integration Name | A display name to identify this integration in Cloudmon, such as "IT Helpdesk". |
| Domain | The full Freshservice host, for example acme.freshservice.com, or just the sub-domain acme. When only the sub-domain is entered, .freshservice.com is added for you. |
| API Key | The API key of the Freshservice agent that Cloudmon uses to create tickets. |
| Requester Email | The email address recorded as the requester on tickets created by Cloudmon, for example monitoring@yourcompany.com. |
Ticket Settings
| Field | Description |
| Ticket Subject | The text used as the ticket 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 ticket: Down, Critical, Trouble and Attention. The matching priority is shown beside each severity: Down is Urgent, Critical is High, Trouble is Medium and Attention is Low. At least one must be selected. |
| Resolve Ticket Automatically When Alarm Clears | Enabled by default. When enabled, Cloudmon resolves the ticket when the alarm clears. When disabled, the ticket 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 a ticket in Freshservice automatically, for the severities selected in the integration.