1<?xml version="1.0" encoding="UTF-8"?>
2<roles xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
3 xsi:noNamespaceSchemaLocation="https://chart/schemas/roles.xsd">
4 <!--
5
6This file allows lists of users to be created and configured to receive email notifications.
7
8The roles system and this file is entirely separate and complementary to multiple older systems:
9 - Event notifications configured in the web tool
10 - Admin users in project settings.py
11 - supervisor daemon configuration
12
13A future enhancement may add a web UI for editing this file and could drop the other systems.
14
15It's not necessary to explicitly define users because they can just be created
16implicitly when a role refers to them. Creating <user> objects explicitly just means they get their
17name configured properly in addition to email address, and might help to organise the file.
18
19See `roles` tool to examine and check this file.
20
21We don't allow individual users to create subscriptions, only roles can subscribe.
22This is to avoid people doing personal configuration which could be lost when
23people move on and to encourage setting up proper roles.
24To get a new notification you can create a role then subscribe to it.
25 -->
26
27 <!-- <user>
28 <username>elson</username>
29 <name>Mike Elson</name>
30 <email>mike.elson@eumetsat.int</email>
31 </user> -->
32
33 <!-- Now we define some roles -->
34 <!-- If an event matches multiple roles containing duplicates of the same person we
35 squash the alerts so they only get one email per event etc -->
36 <role>
37 <!-- <username>sysadmin</username> <!-\- just use this to create a short name to refer to it later -\-> -->
38 <name>Admins</name>
39 <description>Monitoring the whole system - hardware, network, installation of software and
40 managing daemons. Currently they just receive email notifications although a future
41 enhancement may give them permission to start and stop processes.</description>
42 <members>
43 <!-- <username>elson</username> -->
44 <email>Mike Elson <mike.elson@external.eumetsat.int></email>
45 </members>
46 <!-- Any number of lines can be given here each with optional glob style wildcards -->
47 <!-- Types of daemon notification are: started, stopped, crashed, fatal and halt -->
48 <daemon-notification>*</daemon-notification>
49 <job-notification>*</job-notification>
50 </role>
51 <!-- <role>
52 <name>Data admins</name>
53 <description>Users who keep an eye on the dataflow, and need to be informed of any job issues.
54 A future enhancement might also allow these users to create and reschedule jobs</description>
55 <members>
56 </members>
57 <!-\- Job notifications are status change only - a job type that previously completed
58 returns a different state. States are tracked per SID.
59 Timeouts for ingestion jobs also produce job notifications -\->
60 <job-notification>*</job-notification>
61 </role> -->
62<!-- <role>
63 <name>Event testers</name>
64 <description>Receive test events</description>
65 <members>
66 </members>
67 <!-\- <event-notification>ONBOARD-EVENTS</event-notification> -\->
68 <!-\- <event-notification>TEST-DAILY-EVENT</event-notification> -\->
69 </role> -->
70 <role>
71 <name>Report readers</name>
72 <description>People who receive all reports as pdf attachments</description>
73 <!-- <report-notification>*</report-notification> -->
74 <report-notification>DAILY_REPORT</report-notification>
75 <members>
76 <email>Mike Elson <mike.elson@external.eumetsat.int></email>
77 </members>
78 <attach-converted-pdf-instead-of-link>true</attach-converted-pdf-instead-of-link>
79 </role>
80</roles>