Backup Radar now allows our clients to customize the ticketing subject that comes through for Automatic Tickets.
Click on Ticketing -> Custom Ticket Subjects
Click on the question mark shown by the arrow below to see the variables that you can utilize in the subject along with plain text. To the right of the Subject Template you will see an example showing what your subject will look like based on the text you enter and the variables you utilize.
Grouping Options
Policy -> This is a per policy so if you are creating a ticket for each backup policy you have activated in Backup Radar you would adjust this subject.
Company -> If you group tickets by company you will create 1 ticket per company.
Job Name -> If you group tickets by Job Name the system will create one ticket per job name.
Device Name -> If you group tickets by Device Name, the system will create one ticket per device name.
Subject Variables
Inside of these groups you can use variables to show things like the date, status, company etc.
Not all variables can be used in each group. Here is a list of which variables you can use in each group:
All Groupings:
- {date} - Ticket Creation Date (more below on customization of this variable)
- {groupBy} - Properties the ticket is grouped by
- {group} - Group Name
- {status} - Policy Status
- {company} - Policy Company
Policy:
- {device} - Device Name
- {job} - Policy Name
- {method} - Policy Backup Method
Job Name:
- {job} - Policy Name
Device Name:
- {device} - Device Name
You can also format the date to appear as you wish, and it can be translated to different languages and location formats.
Date & Time formatting
The structure to format the date looks like this:
{date|formatting options|locale}
Following are some examples on how to format the date and time:
| Format | Result |
| {date|yyyy-MM-dd HH:mm:ss} | 2019-06-24 20:06:56 |
| {date|dd/MM/yy HH:mm:ss tt|de} | 24.06.19 20:12:32 |
| {date|MM/dd/yy hh:mm:ss tt} | 06/24/19 08:10:40 PM |
Formatting Options
d - MM/dd/yyyy (or your locale's equivalent)
MM - Two digit Month (ex: 05 for May)
MMM - Abbreviated Month (ex: Jun, Jul)
MMMM - Full Month
dd - Two digit Day
ddd - Abbreviated Day of Week (Mon, Tue, etc)
dddd - Full Day of Week (Monday, Tuesday, etc)
yy - Two digit Year
yyyy - Four digit Year
HH - 24 hour clock
hh - 12 hour clock (see tt setting for AM or PM designation)
mm - Minutes
ss - Seconds
tt - AM or PM if using 12 hour time
Locales
You can find a list of locales from the 639-1 column in the table here: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
Setup
The grouping options show up in one of two places. To avoid duplication please make sure if you use alert on failure that those grouping settings match what you have for Automatic Ticketing profiles otherwise you may end up will duplicate tickets. As you can see I have them both set to group by Device Name which would work and not create duplication of tickets.
Alert on Failure
Automatic Ticketing Profiles
If Alert on Failure were set to Policy grouping and Automatic Ticketing were set to Device Name then the system would end up creating new tickets on a per policy basis every time the backup failed. The automatic ticketing would create its own set of tickets on a per device name grouping which would create duplication in your ticketing system.
0 Comments