Approach for Storing Trace IDs for Auditing Changes
anyone saving trace ids to database records on mutate, as a form of auditing, easily tracing back all changes that happened?
or would you rather add the affected database records of a trace into the trace itself, and then query all related traces via the observability platform instead?
or would you rather add the affected database records of a trace into the trace itself, and then query all related traces via the observability platform instead?
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
