datomic 2025-12-15

is anyone who puts code on their transactor classpath perhaps instrumenting this code with tracing a la http://honeycomb.io ? any gotchas to be aware of?

have you inspected https://docs.datomic.com/reference/tx-stats.html#approach? It should cover almost anything you'd want about transactions. I’m a fan of tracing but I'd hesitate to put it inside tx-fns. (You could consider pumping tx-stats to Honeycomb)

thanks @ghadi!

Are these used for transaction functions?

yes, the idea would be to instrument transaction functions in HC

i guess the broader question is, other than via peer-side io-stats, what other methods are there for observing transaction function activity?

datomic.transaction logger

šŸ‘ 1

thank you! is there any way to correlate these logs with the installed d/function transaction function?

Unfortunately, no, unless you write the logger into the tx-fn

1

ah! are we able to emit our own logs into the same log stream as these datomic.transaction logs, then? if so, is there perhaps example code i can follow?

We don't offer that unfortunately, but you can log things yourself somewhere

ok, will give that a go, thank you

I'm curious about how you're gonna install the honeycomb tracer in the transactor, but I'm excited to find out!

šŸ˜… 1

that's why i asked in here, haha. i guess given how it needs to be configured, there is no suitable opportunity to do so

@joe.lane when you say 'log things yourself somewhere' 'into the tx-fn' do you mean logging to the transactor's own log or somehow emitting logs via something we side-car in on the classpath - ie. there's no facility to log to the transactor's own log, right? we have to side-car?

I'd like to revise my statement. Don't try and get logging intertwined with the logging in the Transactor. Do what you were going to do with honeycomb.

thank you!