Difference between revisions of "Log"
| Line 31: | Line 31: | ||
| − | + | '''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 | + | {{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: | 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: | ||
Revision as of 09:57, 22 January 2012
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 
.
.
Messages will be visualized clicking this icon.
.
Messages at WARNING and ERROR levels will be highlighted in red. In case of exceptions this will be substituted by the icon 
Exceptions will be visualized clicking this icon.
DB Log Enabling
GreenVulcano® ESB 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:
- $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).
