ken
looks awesome! I really like the API and the docs. Thanks for sharing ๐
I was looking at https://github.com/conormcd/clj-honeycomb and https://github.com/tendant/clj-telemetry. But having a generic solution with ken
is much nicer!
Building an integration with OpenTelemetry wouldn't be too much effort either if someone likes to use that as backend.
Looking forward to giving ken
a try for some project soon!
Awesome - yeah, we wanted something decoupled from specific sinks, because we also pipe ken events other places, for example our structured JSON logs. Plus, when doing local development itโs super useful to subscribe a pretty-printer and get a dump into your console, or a simple local file appender for later investigation.
have you seen mulog? looks similar to ken at a glance
Yeah, it was announced a bit after weโd built and started using ken internally - definitely a lot of similar ideas
Really cool. Like @hi895 mentioned, otel integration would be ๐
Speaking of that, curious about how people add tracing to pedestal's middleware
right now, exceptions caught in pedestal don't get displayed for us in APM. I suspect it is because we need the equivalent of
try {
runSomething();
} catch (Exception e) {
Otel.captureException(e);
}
wherever pedestal catches exceptions.
@james.r.carr you want to add an interceptor to your interceptor chain
1that does nothing on enter
but on exit looks for an :error
thrown exceptions aren't propagated directly to other interceptors , so that is your way to do