Report Log Configuration

Configuring the report log is easy with InetSoft's Style Intelligence, a powerful business intelligence platform that allows users to make custom log changes. View the example below to learn more about this powerful reporting software solution.

Enterprise Manager provides the ability to log messages generated during server execution. Logged messages are appended to a text file (sree.log, by default) and optionally sent to “stderr”.

Detail level	Description
Finest	Very fine-grained performance information.
Fine	Debugging messages.
Info	Non-critical information messages.
Warning	Non-fatal errors and critical messages.
Severe	Fatal errors.

View more examples in the InetSoft visualization gallery

Request a Personalized Demo

#1 Ranking: Read how InetSoft was rated #1 for user adoption in G2's user survey-based index

Click 'Send Log' to email the log contents to the address specified in the 'Send Log To' field of the 'Log Configuration' page.

From the Enterprise Manager, you can administer the log file by selecting 'Log' > 'Log Configuration' on the navigation tree under the Server tab. You can change the amount of detail that appears in the log file by editing the 'Log Detail Level' value on the 'Log Configuration' page. There are five detail levels defined.

It is recommended that you set the detail level to 'Warning' or higher.

As of version 10.2 logging in InetSoft is implemented using the standard Java Logging API of the java.util.logging package. Log messages and be customized and formatted, without implementing a custom logging mechanism. You can now selectively set different log levels for different packages and include useful context based information within logs.

Note: If there is no 'logging.properties' found by the report server, the basic logging properties will be used from the sree.properties file.

In order to customize your logs, you need to include a 'logging.properties' file within your sree home folder.Consider the sample 'logging.properties' file:

.level=INFO
handlers=java.util.logging.ConsoleHandler,inetsoft.util.log.FileHandler
inetsoft.util.log.FileHandler.fileName=${sree.home}/sree.log
inetsoft.util.log.FileHandler.limit=1048576
inetsoft.util.log.FileHandler.count=2
inetsoft.util.log.FileHandler.formatter=inetsoft.util.log.PatternFormatter
inetsoft.util.log.FileHandler.formatter.pattern=%l %dd-%db-%dY %dH:%dM:%dS %u %c %M %m
inetsoft.sree.web.level=FINE
inetsoft.uql.jdbc.level=FINE

View live interactive examples in InetSoft's dashboard and visualization gallery.

The first property sets the default log level. One Of (FINEST, FINE, INFO, WARNING, SEVERE)

The second property sets the different log handlers. You can implement your own custom handler by implementing the java.util.logging.Logging interface.

The 'filename', 'limit', 'count' and properties specify the log file name its size limit and the number of files to archive.

The format pattern specifies the format of the log message using the following characters.

%lLog level
%dd,%db,%dYLog Date (Day, Month, Year)
%dH:%dM:%dSLog Time (Hour, Minute, Second)
%uUser Name
%cClass Name
%MClass Method
%mLog Message

The 'level' property specifies the log detail lever for a specific package. You can now have finer logging for certain modules, without cluttering the log with messages from other parts.

Report Log Configuration

More Articles About Reporting

More Resources