Superservice- DLF Schema for Database service
- Extended Schemas for the
database
Superservice
Schemas for the dialup
Superservice- DLF Schema for Dialup service
Schemas for the dns
Superservice- DLF Schema for DNS service
Schemas for the dnszone
Superservice- DLF Schema for DNS Zone service
Schemas for the email
Superservice- DLF Schema for Email service
- Extended Schemas for the
email
Superservice
Schemas for the firewall
Superservice- DLF Schema for Firewall service
Schemas for the ftp
Superservice- DLF Schema for FTP service
Schemas for the msgstore
Superservice- DLF Schema for Message Store service
Schemas for the print
Superservice- DLF Schema for Print service
- Extended Schemas for the
print
Superservice
Schemas for the proxy
Superservice- DLF Schema for Proxy superservice
Schemas for the syslog
Superservice- DLF Schema for Syslog superservice
Schemas for the www
Superservice- DLF Schema for WWW service
- Extended Schemas for the
www
Superservice
- Derived Schemas for the
www
Superservice
This chapter documents the available schemas in the
standard Lire suite. For each superservice, the base schema
is explained, followed by any extended and derived schemas.
Schemas for the database
SuperserviceDLF Schema for Database serviceSchema ID:
database
Timestamp Field:
time
A record in the database DLF schema represents
one event in the database. This may be a connection from a client,
a SQL query, etc.
Fields in the Schema -
time
Type: timestamp Defaults: 0 The time at which the event occured. -
user
The name of the user who executed the command. -
remote_host
Type: hostname Defaults: - The host from which the user executed the command. -
action
The command that was executed. Commands you are likely to
encounter are connect,
disconnect, shutdown and
query.
-
database
The database name on which the command was executed. -
query
When the command field is a
query, this field contains the actual SQL
query that was executed.
-
success
Did the command succeeded? -
result
When the success field is
false, i.e. when the command failed, this
field should contains the logged error message. -
connection_id
An "appropriate" "connection label" for the backend that can
be used for session analysis in conjunction with the
timestamp,
username and
database fields. This can be a
connection identifier, a PID, a real session ID or whatever makes
sense in the particular backend.
Extended Schemas for the
database
SuperserviceQuery Type Extended Schema for Database SuperserviceSchema ID:
database-querytype
Base Schema:
database
Module:
Lire::Extensions::Database::DatabaseSchema
Required Fields:
query
An extended schema for the database superservice
which extracts the query type from the query that was made.
Fields in the Schema -
querytype
The type of SQL query that was made. This will be usually be
something like SELECT,
INSERT, UPDATE,
DELETE or other administrative commands. In
the case of nested queries, this will be the type of the
outer-most query.
|