Alex Malek

a possible fix to historical quotes

1

Since things broke when the API changed I wrote this. It relies on the fact that the web page has all the data in json objects. So I pattern match...

take an optional param database to save audit info to

3

allows saving log info not connected to a valid datadase ie failed login with bad DB name consolidate all logging for a cluster

Always redirect STDOUT to logfile

1

When run as a systemd process without the --daemon flag the `print` statements that implicitly use STDOUT do not make it into the logfile

Prevent crash when parsing connection attempt for database that does not exist

1

example csv: ``` 2020-10-06 17:41:28.952 EDT,"foo","foo",32580,"192.168.118.117:50773",5f7ce488.7f44,2,"authentication",2020-10-06 17:41:28 EDT,15/16636,0,LOG,00000,"connection authorized: user=foo database=foo SSL enabled (protocol=TLSv1.2, cipher=ECDHE-RSA-AES256-GCM-SHA384, compression=off)",,,,,,,,,"" 2020-10-06 17:41:28.952 EDT,"foo","foo",32580,"192.168.118.117:50773",5f7ce488.7f44,3,"startup",2020-10-06 17:41:28 EDT,15/16636,0,FATAL,3D000,"database ""foo"" does not exist",,,,,,,,,"" ```

when using pam authentication all logon failures marked as success

3

The issue is when using PAM auth a log msg of level LOG created before the FATAL msg Pass in the msg and check it to catch this case. Example...

Needed to prevent possible session_id collision Backwards compatible with old schema, will append an id or name to session_id Modify audit.sql so it can be run for initial install or...