The GLF plugin now also include automatically highlighting entries highlighted as warning, errors and exceptions and, if you have a BI 4 webi log also has a section which automatically identifies specific user sessions within it so you can easily filter just the one you are interested in. The version at this new link has many (around 60) improvements over the previously version, from new features to stability improvements.
notepad, notepad++). Plugins and configuration files created by experts automatically analyse and tag documents for a user, flagging potential root-cause errors and other important information for ease of access. Filters and tags allow users to only scan for information relevant to the problem they are having, removing much of the need to scroll through an entire log in order to search for relevant information. It is more user-friendly and intuitive than other applications used to perform the same task (e.g. a 4Gb machine can load 18Gb of logs.įLR is one of the tools used by SAP Support Engineers to open and analyse logs in order to find further information regarding error output from SAP Products. Typically, it is possible to open logs which total around 4.5x the available memory on the machine - e.g. FLR is used to open large logs in any text format and can easily scan and find information within them. Use pre-built tags to easily identify common SAP BI log messagesįLR is a log reading application which has been designed to read and analyse text log file, no matter which application has generated it. Read long chains of multiple logs at once with light memory footprint.Very powerful search and filtering options.Reader for SAP BI Platform trace logs (GLFs) and any other text format.This is the official page for the SAP Flexible Log Reader (FLR). New documentation was added to this scn page.Check out the new performance chart for finding areas of slow performance in the logs!
#CAN FLEXI 8 PRODUCE A SECOND PAGE IN A FILE FULL#
See the Release Notes for full details of the updates.This fixed an issue with 4.2 Web Intelligence logs that cause the tool to crash.
0 kommentar(er)
