Overview
Plug-in Notes:
Key Features & Functionality
The Appian Log Reader Plug-in contains functionality to:
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.
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.
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.
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.
Sam Zacks - also, I wasn't notified of your reply until just now when someone clicked "like" on my top comment. I suggest when replying to these you directly tag people and/or click "like" on the comment you're replying to. It seems to me that Community settings should be refined such that people are notified of replies here.
Sam Zacks - your design_errors.csv file would (i presume) need to have some rows in it with the older version of the column set. What do you see when you look?
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?