Log Reader

Also I've found that in the "tail..." function, filtering doesn't seem to work.  I tried a filter that "readCsvLogPaging" was able to use just fine (making sure to adjust to use "filterColumNumber" instead of column name), but it always returns zero results (using either "=" or "contains" operators on a known-good username).

Edit: I just tried the newer "tailCsvLogPaging()" function and I notice it *does* include the quotes around the text column from the same row in question.  Unfortunately it seems the "tail..." function versions don't have a way of setting a start index for paging use, so I'm not sure exactly how to incorporate that into the tool I've previously created to allow paging through the Design_errors log.

Would it be possible to create a new version of the readCsvLog functions that doesn't strip out text-containing quotes as found in the original CSV file?  In particular the "Error Message" column is liable to have text that contains commas, and since each log row is returned as mere plaintext, in order to create a dictionary of data we're forced to use the split() function on commas.  But the function also removes the quote marks around strings that contain commas, so we have no way to verify we're splitting on the right things without really having to make big guesses.  I bring this up now because yet another corner case in the heuristics I was using to read the row data has cropped up, causing extra headaches.

Honestly I'm not sure why this function doesn't return CDT or at least JSON data - that would make it incredibly less of a headache to use.

As a concrete example, here's a row in the CSV file itself showing the error message wrapped in quotes:

Whereas here's the same row, straight out of the readCsvLogPaging() function (notice the quotes have been stripped by the plug-in):

CC: Mark Talbot, Sam Zacks,  April Schuppel

Ok great! I'll look for the update from the community

Mark Talbot - that sounds like a good feature.  I won't be able to test it in our case because I had appian support archive the older design_errors.csv file in all our environments, which proved out my theory that it was breaking because the number of columns changed over time.  But that means I no longer have a version to test this against.  However anyone who has an instance that's been around since the '19 versions or so, should be able to reproduce the issue and test if the new functionality works.

I've added a function that reads the CSV in reverse. Please see if this works for your use case. Note that reading a CSV in reverse is less efficient if you are going to read the whole file than it would be if you read it normally. However, reading the CSV in reverse is more efficient for large files if you are only reading a few lines at a time.

• Additional log functions which start reading from the end of the file

Hi,

I am trying to access rdbms-audit.log.yyyy.MM.dd log which is working fine for active version. The rdbms-audit.log.yyyy-MM-dd log rotates every 10MB and change file name as rdbms-audit.log.yyyy.MM.dd.versionNo. The current version of log reader is not able to recognize this new filename and no data are fetched from it. 

Do we have any resolution or workaround for it ? 

That is my end goal, yes.

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.