Question about Clickhouse DB to Store Accounting

[Ibrahim Almahfooz]

I believe option-2 I mentioned in my prevoius message is something similar
to what Jerry suggested, but I would imagine the linelog has better
customization when it comes to what to log which also gives the flexibility
to log what we are interested + reduce file size.


On Fri, 6 Mar 2026 at 21:04, Ibrahim Almahfooz <ibrahim.nezar at sevennet.net>
wrote:

> Pertaining the concern mentioned by Alan about clickhouse db updates
> queries, if you mean the update statements, well as option-1 what i'm
> trying to writing directly into the ClickHouse database. I was thinking to
> replace the update statements by insert for both Interim-Update and Stop to
> log all accounting triggers instead of updating in-place since what I want
> to track all accounting changes happening per session. Any concerns here
> for this approach?
>
> As option-2 approach, I thought of using the details module, perhaps with
> on hourly %H or minutes %G rotations and then use some thirdparty pipelines
> to parse those and write them in batches into a ClickHouse DB and track the
> files written.
>
> To help having an idea of current accounting rate per minute (peak hours):
> interims: 30k, starts: 500, stops: 1k
>