Fno this is currently not possible.
FCan you describe your use case a little more in detail so we can understand if that would maybe be interesting in ZITADEL?
FI heard something like this with customers... maybe its the same.
Customers wanted to write audit events like when a user does an activity (CRUD on an API) they wanted to emit an audit event into zitadel to have a more complete picture about the users activity.
Customers wanted to write audit events like when a user does an activity (CRUD on an API) they wanted to emit an audit event into zitadel to have a more complete picture about the users activity.
SI’d enjoy this too as we are this week planning our own simple append only audit log service and frankly it’s more annoying than I’d want it to be
FTake it with a lot of salt what I am sharing now 
But I was recently thinking about deploying zitadel with a timescale db for exactly such cases where we (zitadel) wanted to store access, audit, http, action,... logs for further analytics.
Exposing that with an api would not be a big pain once we start working on something like that.
But I was recently thinking about deploying zitadel with a timescale db for exactly such cases where we (zitadel) wanted to store access, audit, http, action,... logs for further analytics.
Exposing that with an api would not be a big pain once we start working on something like that.