User-oriented audit logging vendor?
Posted by BattleBrisket@reddit | ExperiencedDevs | View on Reddit | 3 comments
I've developed about a dozen apps in various industries over my career, and every one of them had a different solution for app-level event logging. I'm talking about tracking business-relevant events within the app, with the express intent of those logs being viewed and utilized by the end users of said app. For example, if my app handles blog posts, the users might have an audit log that track edits to those posts (who made, them, when, what changed, etc.)
Each time this need came up, the ultimate solution we picked fell into one of two camps (or a little of both): open source libraries (usually tied to language ecosystem), and/or roll-your-own minimalist solutions tailored to the specific logging needs.
Over the years I've looked for a vendor-based solution to this need, but I always wind up looking at the same heavyweight "log & monitor any/every thing" approaches, such as Splunk, Dynatrace, ELK stack, New Relic, etc. etc. These allow tremendous logging capability, but cost a fortune (time, money, or both) and are ultimately overkill to deliver on a user-facing feature for audit log visibility.
I'm looking for a solution I can carry from one project to the next, and ideally offload the deep audit log research/reporting to a third party. Am I alone in this need? Has anyone found solutions that fit the bill described above?
Maxion@reddit
This is one of those things where it is hard t vendor. Each situations specific requirements are all over the place, so any vendored approach ends up being complicated.
Mixpanel is one SaaS I've integrated and the integration was at least quite easy, and never became spaghetti. The reporting part was quite meh though (this is 5+ years ago now).
Rea-301@reddit
I’m not sure if I understand why this isn’t simply part of your data model. If you’re tracking change history in a db level - and again maybe I’m just not getting it - why isn’t it a required element in your data store. I.e a blogpost has a db entry with the author and last modified user. Every change I would give it a history and transaction table that gets written to with some age of requirements.
Affectionate_Ad3953@reddit
You're not alone that's for sure.