3 ms·
We use SQLite for logging all the things. This sidesteps entire rabbit colonies worth of issues - especially with regard to downstream parsing & reporting. I h
by bob1029 4y ago
We use SQLite for logging all the things. This sidesteps entire rabbit colonies worth of issues - especially with regard to downstream parsing & reporting.
I have found the extra structure and familiar semantics make it a lot easier to talk about what we log, how we log it and why.
- hckr1292 4y agoCan you saw more about this? I've never heard of anything like this and can't figure out if its genius or silly. Things I'm curious about: * Are you working on a SAAS product or embedded/IoT project or hobby project? * How do you aggregate the SQLite logs together from disparate machines? Seems like you probably can't use fluentbit/filebeat/etc. * Where do you query these logs? * How do you structure these logs? (timestamp, machine, message) or something with more columns? * Are you able to capture stacktraces? I _love_ the idea of leveraging SQLite for this kind of scenario and possibly skipping a lot of messy plumbing or pricy vendors, but I'm uncertain how this works.
- bob1029 4y agoWe ship a B2B product that spools to a log.db when running on client machines. We built in-house tooling that is tailored to obtaining and analyzing copies of these databases. Stack traces, user actions, 3rd party logs, et. al. are meticulously tracked in a schema we thought most appropriate for our business.