I like to do this the PSDK way since I can use that to create configuration snapshots and them just do a file diff to see what has changed when somebody breaks something.
I would go the SQL route as well. PSDK seems like a bit of overhead to run a fairly simple SQL command.
I find it interesting that Genesys still doesn’t have a decent auditing capability for config changes, although I have heard for many years they were going to.
Yes, of course you can. I don’t think of logs as a good aduit tool. I guess I should clarify what I think of as a good audit tool. While you can search through logs, and in theory keep them indefinetly or use a parsing tool to even put them in a database, you still have the overhead of looking through logs or developing a solution to write changes out to a database. As an example, in Avaya, I can simply type list history and even filter by using objects, and I get a list of what changes were made, time, and by which login. Ideally an audit should not only show you time, login, and what change was made, but also what the previous value was so you can revert back if needed. Plus with a database table it is easier to write a UI (or even have a UI) that end users can access so they don’t always have to come to the IT department to get these answers (I know, job security!).