Issue about /api/auditLog
AnsweredI have a issue about /api/auditLog. My costomer want to integrate his website with EZ-Pro. However, the audit log information is produced very fast within a day. When he use this api, the HTTP response is too slow to get terrible user experience.
As shown in the attached, my customer build a website to present EZ-Pro's audit log information. His EZ-Pro Server produce 100000 audit logs every day. When he use /api/auditLog for one day to present the result, it needs almost 5 seconds. When he use /api/auditLog for one month to present the audit logs, it needs a very long time. That is not good user experience. He also classify the audit logs according to audit type by himself, because of only two parameters in /api/auditLog. He hope that we could present Server-Side Paging for /api/auditLog.
For example, someone just want to get the top 50 audit logs quickly, but it doesn't supported now. If there are a lot if audit logs in database, that will take a lot of time. Just for the top 50 audit logs..
As a result, do you plan to modify the parameters of /api/auditLog forServer-Side Paging?
I think it will be the best way to solve the amount of logs issue.
Thank you:)

-
Official comment
Hi @...,
As discussed in the support ticket (#22385) we are not able to reproduce the issue you describe.
And since you informed us that we are not allowed to access the customer's server via internet, there is not much for us to resolve, unless you can provide a clear reproduction scenario.Reducing the number of lines to retrieve most likely won't resolve the issue you encounter.
In normal circumstances you can retrieve the whole audit trial in less within milliseconds with the API call.
Please sign in to leave a comment.
Comments
1 comment