Microservices audit/change tracking

We’re running a platform with around 100 or so microservices (mix of nodejs, dotnet and python). We have audit logging today for some critical paths but each service has invented their own pattern and the data is not really useable unless there is some type of incident then we can manually pull it.

We more and more often find ourselves in a situation where we have the need to track/audit certain types of changes. Practically what we need is a “who changed what” across many different services. Especially when support people modify things in our Backoffice tool 🙂

I wonder if you has a solution or pattern for change tracking that can span multiple services and keep track of the “context” across a transaction spanning multiple services? (like which user initiated the change).

Or am I going about this the wrong way? Any input and experiences on how you have handled change/audit tracking for similar scenarios would be very interesting to hear about!

submitted by /u/nailefss
[link] [comments]

from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/3pRcDzq

Leave a comment

Design a site like this with WordPress.com
Get started
search previous next tag category expand menu location phone mail time cart zoom edit close