File: database.xml

package info (click to toggle)
lire 2%3A2.0.2-3
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 13,480 kB
  • ctags: 5,059
  • sloc: perl: 61,803; xml: 18,361; sh: 1,834; makefile: 1,359
file content (87 lines) | stat: -rw-r--r-- 2,919 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE lire:dlf-schema PUBLIC
  "-//LogReport.ORG//DTD Lire DLF Schema Markup Language V1.1//EN"
  "http://www.logreport.org/LDSML/1.1/ldsml.dtd">
<lire:dlf-schema superservice="database" timestamp="time"
 xmlns:lire="http://www.logreport.org/LDSML/">

 <lire:title>DLF Schema for Database service</lire:title>

 <lire:description>
  <para>A record in the <type>database</type> DLF schema represents
   one event in the database. This may be a connection from a client,
   a SQL query, etc.
  </para>
 </lire:description>

 <lire:field name="time" type="timestamp" label="Timestamp">
  <lire:description>
   <para>The time at which the event occured.</para>
  </lire:description>
 </lire:field>

 <lire:field name="user" type="string" label="User">
  <lire:description>
   <para>The name of the user who executed the command.</para>
  </lire:description>
 </lire:field>

 <lire:field name="remote_host"	type="hostname" label="Client Host">
  <lire:description>
   <para>The host from which the user executed the command.</para>
  </lire:description>
 </lire:field>

 <lire:field name="action" type="string" label="Query Action">
  <lire:description>
   <para>The command that was executed. Commands you are likely to
    encounter are <constant>connect</constant>,
    <constant>disconnect</constant>, <constant>shutdown</constant> and
    <constant>query</constant>. 
   </para>
  </lire:description>
 </lire:field>

 <lire:field name="database" type="string" label="">
  <lire:description>
   <para>The database name on which the command was executed.</para>
  </lire:description>
 </lire:field>

 <lire:field name="query" type="string">
  <lire:description>
   <para>When the <structfield>command</structfield> field is a
    <constant>query</constant>, this field contains the actual SQL
    query that was executed.
   </para>
  </lire:description>
 </lire:field>

 <lire:field name="success" type="bool" label="Success?">
  <lire:description>
   <para>Did the command succeeded?</para>
  </lire:description>
 </lire:field>

 <lire:field name="result" type="string" label="Error">
  <lire:description>
   <para>When the <structfield>success</structfield> field is
    <constant>false</constant>, i.e. when the command failed, this
    field should contains the logged error message.</para>
  </lire:description>
 </lire:field>

 <lire:field name="connection_id" type="int" label="Connection ID">
  <lire:description>
   <para>An "appropriate" "connection label" for the backend that can
    be used for session analysis in conjunction with the
    <structfield>timestamp</structfield>,
    <structfield>username</structfield> and
    <structfield>database</structfield> fields. This can be a
    connection identifier, a PID, a real session ID or whatever makes
    sense in the particular backend.
   </para>
  </lire:description>
 </lire:field>

</lire:dlf-schema>