by PaulAnunda on 10/26/20, 2:33 PM with 1 comments
by PaulAnunda on 10/26/20, 2:34 PM
At previous gigs, I've had to either implement audit logging from scratch or integrate my service with preexisting internal solutions. Typically, a table within the primary DB would be used (leading to space issues), search would be slow or non-existent (can't search - won't use), or there would be little to no documentation on how to best utilize the tooling.
Despite these shortfalls, I saw the benefits of having audit logging in place. Customers could keep an eye on the activity occurring within their account, customer support could root-cause customer issues quicker, and product/engineering teams could gauge feature adoption.
I built AuditAPI to scratch my own itch — to simplify the process of both storing and retrieving audit events.
I'd love to get your feedback, answer any questions, and hear your ideas. Thanks for your time!