Add a ticketing recipient

Ticket Details

Select the HaloPSA ticket type from the dropdown.

Select the ticket category.

Select the importance of the service ticket that will be created as determined by the severity and impact of the issue.

Notifications Settings

This tab allows you to configure the actions when there is a notification:

• How HaloPSA will behave when an alert is triggered in N-able N-central.
• What happens when N-able N-central detects that an issue has gone back to a Normal state.
• How N-able N-central will handle repeat failures.

Select Acknowledge N-central Alerts when a Ticket is Created allow N-able N-central to automatically acknowledge subsequent alerts and prevent further notifications.

For Ticket Section select the section of the ticket to append notes to:

• The Detail Description section of the ticket.
• The Resolution section of the ticket.

When closing a ticket, N-able N-central always writes to the Resolution section.

For When an issue returns to normal:

These settings allow you to determine when and how to change the Ticket status if the issue returns to Normal.

You may not want N-able N-central to change the ticket status, or you may want N-able N-central to change the status to a specific status. Additionally, you can tell N-able N-central what status the ticket must be in before it can make a change to the status.

1. Select Do not change the Ticket Status if you do not want N-able N-central to change the ticket status when the issue returns to Normal. This is the default for this option.
2. Select Change the Ticket Status to if you want N-able N-central to change the status of the ticket to a different status.
   1. Specify the state to which the ticket will be changed.
   2. In the Ticket Statuses column, select and move the status that the ticket must already have before it can be changed. This says to N-able N-central, it's okay to go ahead and change the status of the ticket if it is in one of these statuses.

This feature allows you to configure what will happen to a ticket when an issue reoccurs on a device within a given time period.

The first time a service on a device fails, N-able N-central opens a time window during which the service can transition between states before another ticket will be generated. Within this time window, N-able N-central will not generate a new ticket, but instead it will either update the existing ticket or if the ticket has been closed it will reopen it.

If a ticket remains open beyond the time window, N-able N-central will continue to update it until N-able N-central detects that it is closed, at which time N-able N-central will create a new ticket.

If N-able N-central cannot detect that a ticket has been closed in the PSA solution, N-able N-central will continue to update it until N-able N-central detects that the ticket is closed, regardless of the time window.

For example, if a CPU service on a device goes Failed and generates a ticket, N-able N-central will allow the service to transition between Failed and Normal for 120 hours (the default), or until N-able N-central detects that the ticket is closed.

1. If you do not want N-able N-central to reopen tickets after they have been closed within the specified time window, select Do not reopen tickets.

2. To specify a time period before tickets will be reopened, select Reopen tickets within <specify hours, the default is 120 > hours of ticket creation.

   1. Change the Ticket Status to specify the state to which the ticket will be changed.
   2. In Ticket Statuses, select and move the status that the ticket must already have before it can be changed. This says to N-able N-central, it's okay to go ahead and change the status of the ticket if it is in one of these statuses.

This sections allows you to configure how N-central will decide if Windows Event Log issues are duplicates on particular device and if a ticket should be updated or a new ticket should be opened.

Depending on what sort of event log monitoring you are doing, and what sort of event log entries the applications on a device perform, matching on ID and Source may be sufficient to determine a duplicate.

All properties are included by default.

Select the properties of a Windows Event Log alert that should be used to determine if an existing ticket is updated or if a new ticket will created:

• ID
• Source
• Description

Associated Notification Profiles

This tab allows you to view and set notification profiles and escalation preferences for the Ticketing Recipient. This association of Ticketing recipient and notifications can also be done within the Notification profile itself.

Select an SO or Customer/Site to view associated notification profiles.

From the list of N-able N-centralnotification profiles, select the profile or profiles for the Ticketing Recipient under Primary Notification. As a result, the first notification triggered will be generated in the PSA.

If required, select and specify the rest of the settings for the notification as it will generated in the PSA.

Notification Schedule

This tab allows you to set restrictions that specify when ticket creation can occur.

To configure time periods to which the creation of tickets will be restricted, select one of the following:

• Entire Day - tickets may be created at any time during the day.
• Daily Interval - tickets will only be created during the scheduled notification periods.

If Daily Interval is selected as the Schedule Type, select the time of day for starting the restricted period during which tickets can be created. Before this time, tickets can not be created.

If Daily Interval is selected as the Schedule Type, select the time of day to end the restricted period during which tickets can be created. After this time, tickets can not be created.