Open the menu

    Portal Logs

    Through the administration of Log Files, it is possible to view and delete the files generated in subdirectories of the folder “lumisdata/log" during product manipulation.

    By default, the logs generated by the portal are segmented into the following files:

    • lumisdata/log/lumis/full/logfull.log: displays debugs of classes that are not solely from the lumis package;
    • lumisdata/log/lumis/debug/lumis-debug.log: displays all debugging messages from the portal;
    • lumisdata/log/lumis/info/lumis-info.log: displays debugging messages from the portal, from info level and above;
    • lumisdata/log/lumis/sendmail/sendmail.log: logs information about the sent email (subject, from, to, cc, among others);
    • lumisdata/log/lumis/serialization/serialization.yyyy-mm-dd.log: logs the import process. The log is off by default (level: info) in the logger with name lumisservice.lumis.service.portalmanagement.serialization. To enable the log, you must change its level to "debug", as well as the level of the global filter (thresholdFilter) at the end of the file. It is recommended not to keep the level at debug after investigations since it generates a lot of information;
    • lumisdata/log/lumis/httpintegration/httpintegration.log: logs messages from the HTTP Integration API. The log by default displays messages at the info level from the logger named lumisservice.lumis.portal.httpintegration. To display more specific details of HTTP calls, you must change its level to "debug", as well as the level of the global filter (thresholdFilter) at the end of the file. It is recommended to use the log only as a last resort, giving preference to monitoring information in the big data repository, because the level in debug generates a lot of information;
    • lumisdata/log/lumis/banner/bannerClicks.yyyy-mm-dd.log: logs which banner was clicked, from which environment, and for each banner, it provides the session id, id, name, login, and language of the session user. The suffix of the filename consists of “yyyy” (corresponds to the year), “mm” (corresponds to the month) and “dd” (corresponds to the day). Each record in the created daily file corresponds to a click on the banner;
    • lumisdata/log/lumis/banner/bannerViews.yyyy-mm-dd.log: logs the same information as the banner clicks log, in addition to the URL of the accessed page that contains the logged banner. Each record in the created daily file corresponds to an access to the page that contains the banner;
    • lumisdata/log/lumis/navigation/navigation.yyyy-mm-dd.log: logs each accessed page, starting from the root channel of the portal. Furthermore, it displays information about the session and user, such as id, name, login, and language. Each record in the daily file corresponds to a navigated page by any users;
    • lumisdata/log/lumis/audit/audit.yyyy-mm-dd.log: logs audit entries.

    It is possible to view the log in real-time through the Console Output option.

    These files can also be accessed directly in the directory from lumisdata/log, or through the Configuration section --> Information --> Portal Logs, where they are grouped by "Banners", "Import and Export", "Email Sending", "Navigation" and "All", in the latter case, all logs are displayed recursively, including lumis-debug and lumis-info as shown in the figure below:

    To save on the server, log files that are local or on other servers that are not the application server, it is necessary to activate "Send File" and provide:

    • File: In this field, the file.log that is located in a local directory or another server is assigned. Just locate it by clicking on "Browse";
    • Subdirectory: In this field, the subdirectory created in “lumisdata/log" of the application server is provided.If the subdirectory is not specified, the file will be saved in the root "lumisdata/log".

    For the other administrative areas of log, the "Send File" option is not recursive. Thus, it is not possible to assign a subdirectory.

    For example, in the administrative area of log for "Email Sending," when triggering "Send file," only the file that is local or on another server is informed. Upon confirmation, the file will be saved in the root "lumisdata/log/lumis/sendmail" of the application server.