[<<][softarch][>>][..]

Sat Feb 22 10:21:05 EST 2020

Better logging? A two-level approach.

This is a Goldilocks problem: too little and you don't have what you
need, too much and dealing with volume is problematic.

How to better encode logging?

I like the idea of giving each log statement a tag.  This way logging
is not more than timestamp + tag + data, and it can go in a sqlite
database.

Many large volume problems benefit from a two-level approach: in this
case:

1. sqlite tags can be used to limit the volume

2. ad-hoc structural filtering can be used at the finer scale.

The problem I am trying to avoid is to have to design a query
language.  Sqlite is neat because the second level matching could be
implemented as C predicates operating on encoded data strings.

[Reply][About]

[<<][softarch][>>][..]