1GLITE-LB-LOGEVENT(1) Logging&Bookkeeping GLITE-LB-LOGEVENT(1)
2
3
4
6 glite-lb-logevent - program for logging events to L&B subsystem
7
8
10 glite-lb-logevent -s Application -e UserTag -j JOBID -c SEQCODE --name
11 NAME --value VALUE
12
13
15 glite-lb-logevent is a low-level program for logging events to the L&B
16 service. It is used internally by WMS components and has many more
17 options, that are not recomend to be used at the user level. At the
18 user level it is supposed to be used only for logging user tag events.
19
20
22 Besides NAME and VALUE of the tag, which are user defined, the user has
23 to specify a valid JOBID, and SEQCODE (L&B event sequence code).
24
25 The user application is always executed from within a JobWrapper
26 script. The wrapper sets the appropriate JobId in the environment vari‐
27 able EDG_WL_JOBID. The user should pass this value to the -j option of
28 glite-lb-logevent.
29
30 Similarly, the wrapper sets an initial value of the event sequence code
31 in the environment variable EDG_WL_SEQUENCE_CODE. If the user applica‐
32 tion calls glite-lb-logevent just once, it is sufficient to pass this
33 value to the -c option. However, if there are more subsequent calls,
34 the user is responsible for capturing an updated sequence code from the
35 stdout of glite-lb-logevent and using it in subsequent calls. The L&B
36 design requires the sequence codes in order to be able to sort events
37 correctly while not relying on strictly synchronized clocks.
38
39
41 The example bellow is a job consisting of 100 phases. A user tag phase
42 is used to log the phase currently being executed. Subsequently, the
43 user may monitor execution of the job phases as a part of the job sta‐
44 tus returned by L&B.
45
46 #!/bin/sh
47
48 for p in `seq 1 100`; do
49
50 # log the UserTag event
51 EDG_WL_SEQUENCE_CODE=`glite-lb-logevent -s Application
52 -e UserTag
53 -j $EDG_WL_JOBID -c $EDG_WL_SEQUENCE_CODE
54 --name=phase --value=$p`
55
56 # do the actual computation here
57 done
58
59
60
61
62
64 See command line help (glite-lb-logevent -h) for extensive help on all
65 options. However, EDG users should should follow the usage shown in
66 SYNOPSIS strictly. Logging other events may confuse the L&B service
67 and cause wrong job status information to be reported.
68
69
71 No configuration files needed.
72
73
75 Please report all bugs to CESNET gLite L&B issue tracker available at
76 https://github.com/CESNET/glite-lb/issues
77
78
80 glite-lb-bkserverd(8), glite-lb-interlogd(8), glite-lb-logd(8)
81
82
84 EU EGEE, JRA1.
85
86
87
88EU EGEE Project April 2008 GLITE-LB-LOGEVENT(1)