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

Parents

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
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
Sam Zacks over 4 years ago in reply to Mike Schmitt

That is my end goal, yes.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Mike Schmitt over 4 years ago in reply to Sam Zacks

Sam Zacks - do you mean a fix to the plug-in? That seems like it would be useful, since otherwise any future alterations to the columns of a log file will seemingly have the same "breaking" effect.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Sam Zacks over 4 years ago in reply to Mike Schmitt

You're correct about this - I understand the issue is when there are inconsistent column sets. I'm continuing to investigate changes and trying to reproduce so that I can prove out a fix.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Mike Schmitt over 4 years ago in reply to phorning

phorning - I had Appian Support deprecate the existing design_errors.csv files across all my environments, such that a new file has been created as of a few days ago, so that there is now a consistent number of columns across all rows. Per my expectation, the log reader query now works fine.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Mike Schmitt over 4 years ago in reply to Sam Zacks

Sam Zacks - for further clarification: I've had Appian Support deprecate the existing design_errors.csv in all my environments so that they can start over with consistent columns in all rows, and the log reader query now works fine, as I'd expected.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Comment

Mike Schmitt over 4 years ago in reply to Sam Zacks

Sam Zacks - for further clarification: I've had Appian Support deprecate the existing design_errors.csv in all my environments so that they can start over with consistent columns in all rows, and the log reader query now works fine, as I'd expected.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Children

No Data