1 |
02482b9a
|
Alessandro_N
|
# datasets_Monitoring README
|
2 |
|
|
#
|
3 |
|
|
# Alessandro Nastasi, April 2015
|
4 |
|
|
#
|
5 |
|
|
|
6 |
|
|
This is a script aimed at monitoring the status of the Sitools2 datasets
|
7 |
|
|
and the mapping of their fields.
|
8 |
|
|
|
9 |
|
|
Put the script in the Sitools2 folder data/datasets(/map, for the latest versions)
|
10 |
|
|
where the datasets information are stored as xml files.
|
11 |
|
|
Then, read and record the current status/mapping, with:
|
12 |
|
|
|
13 |
|
|
$ datasets_Monitoring --record
|
14 |
|
|
|
15 |
|
|
The datasets properties are locally stored in files named as:
|
16 |
|
|
|
17 |
|
|
<dataset_name>.lastStatus.xml
|
18 |
|
|
|
19 |
|
|
The '--record' option should be executed manually by the administrator every time
|
20 |
|
|
one or more datasets are modified (it would be good to add a reminder to the
|
21 |
|
|
Sitools2 pop-up message).
|
22 |
|
|
|
23 |
|
|
To check the datasets mapping/status, launch the script with the '--check' option:
|
24 |
|
|
|
25 |
|
|
$ datasets_Monitoring --check
|
26 |
|
|
|
27 |
|
|
This performs a consistency check between the current (int@*.xml or map/string@*.xml)
|
28 |
|
|
and the last recorded status (<dataset_name>.lastStatus.xml).
|
29 |
|
|
If any inconsistency is found, an alert e-mail is sent.
|
30 |
|
|
|
31 |
|
|
The '--check' option should be run daily and automatically by the system.
|
32 |
|
|
|
33 |
|
|
@author: Alessandro NASTASI for IAS 27-04-2015
|