Log - Revision history

Anonymous at 10:50, 8 March 2012

2012-03-08T10:50:40Z

Anonymous at 10:36, 7 March 2012

2012-03-07T10:36:04Z

Anonymous at 16:38, 30 January 2012

2012-01-30T16:38:26Z

Anonymous at 14:04, 24 January 2012

2012-01-24T14:04:13Z

Anonymous at 09:57, 22 January 2012

2012-01-22T09:57:57Z

Anonymous at 14:10, 18 January 2012

2012-01-18T14:10:52Z

Anonymous: Created page with "This section visualizes the log messages stored into the database. The logs messages can be filtrated to the service name (also partial), client system (also partial) and transa..."

2012-01-17T16:45:54Z

Created page with "This section visualizes the log messages stored into the database. The logs messages can be filtrated to the service name (also partial), client system (also partial) and transa..."

New page

This section visualizes the log messages stored into the database.

The logs messages can be filtrated to the service name (also partial), client system (also partial) and transaction ID, by log level, and research time interval.

The log level is hierarchical, that's mean if it is filtered by INFO, it would by selected also the WARNING and ERROR messages.

The messages are paginated by groups of 100. This limit can be modified by the user.

Big messages (> 500 characters) will be substituted by the icon [[File:GVConsoleLogBigMessIcon.jpg]].

[[File:GVConsoleLogMess.jpg]].

Messages will be visualized clicking this icon.

[[File:GVConsoleLogMessView.jpg]].

Messages at WARNING and ERROR levels will be highlighted in red. In case of exceptions this will be substituted by the icon [[File:GVConsoleLogExcIcon.jpg]]

[[File:GVConsoleLogMessRed.jpg]]

Exceptions will be visualized clicking this icon.

[[File:GVConsoleLogExcView.jpg]]

==DB Log Enabling==

{{GVESB}} includes the "Log viewer" console prepared for accessing to a Oracle database. The connection is done through the parameters defined in the ''GVAdapters.xml'' file of the ''GVJDBCConnectionBuilder'' section. The statement for interacting with the DB are configurated into the GVSupport.xml file in the LogConsole section. The Log4J logger enabling for writing into the DB is done in the GVSupport.xml file into the GVLog4JConfiguration section (disable by default).

The ddl scripts for defining the DB data structure and the configuration fragments for adding/rewriting into ''GVSupport.xml'' and ''GVAdapters.xml'' are in the directories:

* $GV_HOME/doc/extra/log/mysql
* $GV_HOME/doc/extra/log/oracle

Configuration fragments must be adequate to the specific connection parameters for the DB (url, user, password).

← Older revision		Revision as of 10:50, 8 March 2012
Line 46:		Line 46:


−	{{GVESB}} includes the "Log viewer" console prepared for accessing to an Oracle database. The connection is done through the parameters defined in the ''GVAdapters.xml'' file of the [[GVJDBCConnectionBuilder]] section. The statements for interacting with the DB are configured into the ''GVSupport.xml'' file in the [[LogConsole]] section. The Log4J logger enabling for writing into the DB, is done in the ''GVSupport.xml'' file from the [[GVLog4JConfiguration]] section (disable by default).	+	{{GVESB}} includes the "Log viewer" console prepared for accessing to an Oracle database. The connection is done through the parameters defined in the ''GVAdapters.xml'' file of the [[GVJDBCConnectionBuilder]] section. The statements for interacting with the DB are configured into the ''GVSupport.xml'' file in the LogConsole section. The Log4J logger enabling for writing into the DB, is done in the ''GVSupport.xml'' file from the [[GVLog4JConfiguration]] section (disable by default).

	The ddl scripts for defining the DB data structure and the configuration fragments for adding/rewriting into ''GVSupport.xml'' and ''GVAdapters.xml'' are in the directories:		The ddl scripts for defining the DB data structure and the configuration fragments for adding/rewriting into ''GVSupport.xml'' and ''GVAdapters.xml'' are in the directories:

← Older revision		Revision as of 10:36, 7 March 2012
Line 46:		Line 46:


−	{{GVESB}} includes the "Log viewer" console prepared for accessing to a Oracle database. The connection is done through the parameters defined in the ''GVAdapters.xml'' file of the ''GVJDBCConnectionBuilder'' section. The ~~statement~~ for interacting with the DB are ~~configurated~~ into the ''GVSupport.xml'' file in the LogConsole section. The Log4J logger enabling for writing into the DB, is done in the ''GVSupport.xml'' file from the ''GVLog4JConfiguration'' section (disable by default).	+	{{GVESB}} includes the "Log viewer" console prepared for accessing to an Oracle database. The connection is done through the parameters defined in the ''GVAdapters.xml'' file of the [[GVJDBCConnectionBuilder]] section. The statements for interacting with the DB are configured into the ''GVSupport.xml'' file in the [[LogConsole]] section. The Log4J logger enabling for writing into the DB, is done in the ''GVSupport.xml'' file from the [[GVLog4JConfiguration]] section (disable by default).

	The ddl scripts for defining the DB data structure and the configuration fragments for adding/rewriting into ''GVSupport.xml'' and ''GVAdapters.xml'' are in the directories:		The ddl scripts for defining the DB data structure and the configuration fragments for adding/rewriting into ''GVSupport.xml'' and ''GVAdapters.xml'' are in the directories:

@@ Line 10: / Line 10: @@
 [[File:GVConsoleLogMess.jpg|thumb|Big messages]].
-Big messages (> 500 characters) will be substituted by the icon [[File:GVConsoleLogBigMessIcon.jpg]].
+Big messages (> 500 characters) will be substituted by the icon. [[File:GVConsoleLogBigMessIcon.jpg]]
-[[File:GVConsoleLogMessView.jpg|thumb|Big message visualization]].
+[[File:GVConsoleLogMessView.jpg|thumb|Big message visualization]]
 These messages will be visualized clicking this icon.

@@ Line 10: / Line 10: @@
-[[File:GVConsoleLogMess.jpg]].
+[[File:GVConsoleLogMess.jpg|center|thumb|600px|Big messages]].
 Messages will be visualized clicking this icon.
-[[File:GVConsoleLogMessView.jpg]].
+[[File:GVConsoleLogMessView.jpg|center|thumb|600px|Big message visualization]].
@@ Line 21: / Line 21: @@
-[[File:GVConsoleLogMessRed.jpg]]
+[[File:GVConsoleLogMessRed.jpg|center|thumb|600px|Messages with errors]]
@@ Line 27: / Line 27: @@
-[[File:GVConsoleLogExcView.jpg]]
+[[File:GVConsoleLogExcView.jpg|center|thumb|600px|Exception details]]

@@ Line 1: / Line 1: @@
-This section visualizes the log messages stored into the database.
+[[File:GVConsoleLog.jpg|thumb|Log viewer]]
 The logs messages can be filtrated to the service name (also partial), client system (also partial) and transaction ID, by log level, and research time interval.
@@ Line 7: / Line 9: @@
 The messages are paginated by groups of 100. This limit can be modified by the user.
-Big messages (> 500 characters) will be substituted by the icon [[File:GVConsoleLogBigMessIcon.jpg]].
+[[File:GVConsoleLogMess.jpg|thumb|Big messages]].
 Messages at WARNING and ERROR levels will be highlighted in red. In case of exceptions this will be substituted by the icon [[File:GVConsoleLogExcIcon.jpg]]
 Exceptions will be visualized clicking this icon.
-[[File:GVConsoleLogExcView.jpg|center|thumb|600px|Exception details]]

@@ Line 31: / Line 31: @@
-==DB Log Enabling==
+'''DB Log Enabling'''
-{{GVESB}} includes the "Log viewer" console prepared for accessing to a Oracle database. The connection is done through the parameters defined in the ''GVAdapters.xml'' file of the ''GVJDBCConnectionBuilder'' section. The statement for interacting with the DB are configurated into the GVSupport.xml file in the LogConsole section. The Log4J logger enabling for writing into the DB is done in the GVSupport.xml file into the GVLog4JConfiguration section (disable by default).
+{{GVESB}} includes the "Log viewer" console prepared for accessing to a Oracle database. The connection is done through the parameters defined in the ''GVAdapters.xml'' file of the ''GVJDBCConnectionBuilder'' section. The statement for interacting with the DB are configurated into the ''GVSupport.xml'' file in the LogConsole section. The Log4J logger enabling for writing into the DB, is done in the ''GVSupport.xml'' file from the ''GVLog4JConfiguration'' section (disable by default).
 The ddl scripts for defining the DB data structure and the configuration fragments for adding/rewriting into ''GVSupport.xml'' and ''GVAdapters.xml'' are in the directories: