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

Sam Zacks over 4 years ago in reply to Mike Schmitt

Hi Mike, I am trying to reproduce what you have described on a 20.3.90.0 environment and it is not occurring. Are you still on 20.2 and are you still experiencing this issue?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
phorning over 4 years ago in reply to Mike Schmitt

Mike- based on your initial post and your reply below you'd thought that "around the upgrade to 20.2" the design_errors.csv log reader feed broke. But maybe it was a simple fix to include the new columns?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Mike Schmitt over 4 years ago in reply to phorning

I'm not having any 20.2 issue, so I'm not clear what you mean or what the relevance is to this particular issue thread? You might be referring to the one paulc noted in the prior top-level thread, in which case it might be most helpful to reply there and weigh in.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
phorning over 4 years ago in reply to April Schuppel

Hi Mike Schmitt and Somnath Dey any update on the 20.2 issue?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
April Schuppel over 4 years ago in reply to Mike Schmitt

Hi Mike Schmitt - I've reached out to the author to see if they can assist with the issue.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Mike Schmitt over 4 years ago in reply to Mike Schmitt

After some additional troubleshooting, my theory is that the CSV Log Reader fails due to the fact that around the upgrade to 20.2, the design_errors log picked up several extra columns (and because this was just appended to the same log file, instead of the existing file being archived and a new one begun).
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Mike Schmitt over 4 years ago in reply to Mike Schmitt

Is anyone monitoring comments here? April Schuppel perhaps? I have a use case that requires me to be able to query this log file into the Appian UI, and no other workable ways have really been presented to us.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Mike Schmitt over 4 years ago

I'm trying to read the contents of "design_errors.csv" (which appears to be a normally-formatted CSV file). I've tried readCSVLog(), readCSVLogPaging(), and readCSVLogPagingWithHeaders(); all of them fail to pull back any contents. They do receive the header column names from the CSV file, but return no rows of data. Any suggestions?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
paulc919 over 4 years ago

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
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
arjunv489 over 4 years ago

Hi All,

Does this plugin has restriction in the logs it supports, I have recently tried to read sites.csv and users.csv and it always returns blank data. Any inputs will be helpful.

Regards,

Arjun.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel