Log Reader

Overview

Plug-in Notes:

  • Allows only System Administrators or members of the Designers group to access log data.  
  • Does not load files outside the logs directory or files that do not end in .log.* or .csv.*.
  • On multi-application-server environments, logs will only be shown from a single application server.
  • Custom headers can be specified as an optional parameter. This is meant to be used for .csv files that don't contain a header.

Key Features & Functionality

The Appian Log Reader Plug-in contains functionality to:

  • Read files in the Appian /log folder (.csv or .log) and return them as structured data
  • Aggregate data from a .csv file
  • Serve as the source for a service-backed record for viewing logs
  • The Log Reader application provided with the download demonstrates a service-backed record for viewing logs, as well as reports on specific log files. Administrators can view reports on system health over time, including design best practices, system load, and database performance. The application also contains a process that checks details from system.csv and alerts administrators if memory or CPU utilization exceeds a threshold.
  • Tail a log file with tailcsv and taillog. Note that tail is an expensive operation which is optimized for reading the last few lines of a large log file. It's not advisable to tail the entire log file from the end to the beginning. However, tail will perform much better than the other log functions when reading the last few lines from a very large log file. Use the batch size and timestamp filters to limit the number of lines read by the tailcsv and taillog functions.
  • Takes a line of text in CSV format and returns a text array
Anonymous
Parents
  • Since we've upgraded to 20.2 and / or deployed the latest version of this plug in, the System Logs record source no longer brings back any system logs to click on for further information.

    I would suspect its the latest version of the plug in where the function systemlogsrecordtypesource or getloginfo requires the explicit relative path to find the logs ?

    Testing in our non HA environments and the function works correctly, whereas in HA we are getting a null value datasubset.

    Has anyone else found the same with a solution to workaround ? 

    Cheers

  • Hi , did you find a solution for this?

  • Afraid not . I'm hoping those that have good java skills can look at the function where a null value data subset is being returned. Mind you the plug in has been updated in February so I'll need to check again to see if the latest version addresses this issue. 

Comment Children
No Data