Closed myronkscott closed 4 years ago
@saurabhagas or @mathieucarbou Is audit logging going to be used at bootstrap or only runtime?
@saurabhagas or @mathieucarbou Is audit logging going to be used at bootstrap or only runtime?
Both - there's some audit logging during server startup (e.g. parsing whitelist file), and other during runtime (e.g. connections from clients)
@saurabhagas or @mathieucarbou Is audit logging going to be used at bootstrap or only runtime?
Both - there's some audit logging during server startup (e.g. parsing whitelist file), and other during runtime (e.g. connections from clients)
this is problematic in the current implementation. This service is bootstrapped itself very late so is not available during configuration.
@saurabhagas or @mathieucarbou Is audit logging going to be used at bootstrap or only runtime?
Both - there's some audit logging during server startup (e.g. parsing whitelist file), and other during runtime (e.g. connections from clients)
this is problematic in the current implementation. This service is bootstrapped itself very late so is not available during configuration.
@saurabhagas : the way we have implemented the auditing by decorating the DC service and using the listeners, the audit logs methods are only called when the server has reached a final state (like STARTING, ACTIVE, etc).
The PR is here @myronkscott if you want to have a look at what was done: https://github.com/Terracotta-OSS/terracotta-platform/pull/757
@myronkscott what are the next steps for this PR? Do we merge so that that tc-core changes can be done based on the new API?
Provide a way for any component to write messages to the audit logs of the server.