You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Micro services generate auxiliary events (or audits) and data/insights as part of request-response. We could have a framework which enables developers to easily tag what data to generate, aggregate (multiple events for one request to server) and ingest into sinks for further processing/analytics/auditing etc in a sync or async fashion.
Though this will be always-on (as against on-demand tracing) and fully ingested into sinks (as against sampling in tracing), this won't cover "transactional audit" use cases.
The text was updated successfully, but these errors were encountered:
@pmohankumar We have implemented something similar for one of our projects.
The basic idea was to add Annotation based audit to any api ,where few data points like request params are audited by default and developers can add more context to be audited from within the API implementation.
Micro services generate auxiliary events (or audits) and data/insights as part of request-response. We could have a framework which enables developers to easily tag what data to generate, aggregate (multiple events for one request to server) and ingest into sinks for further processing/analytics/auditing etc in a sync or async fashion.
Though this will be always-on (as against on-demand tracing) and fully ingested into sinks (as against sampling in tracing), this won't cover "transactional audit" use cases.
The text was updated successfully, but these errors were encountered: