This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-21
Channels
- # beginners (201)
- # boot (125)
- # cider (3)
- # cljs-dev (21)
- # cljsrn (165)
- # clojars (8)
- # clojure (332)
- # clojure-belgium (1)
- # clojure-gamedev (8)
- # clojure-russia (75)
- # clojure-spec (25)
- # clojure-uk (96)
- # clojurebridge (2)
- # clojurescript (130)
- # code-reviews (16)
- # cursive (26)
- # datomic (20)
- # devops (6)
- # emacs (6)
- # hoplon (90)
- # jobs (9)
- # luminus (2)
- # off-topic (4)
- # om (65)
- # onyx (5)
- # pedestal (4)
- # protorepl (6)
- # re-frame (34)
- # reagent (12)
- # ring (4)
- # ring-swagger (7)
- # specter (2)
- # test-check (8)
- # untangled (2)
- # vim (1)
- # yada (6)
my transaction function works correctly with the in-memory db but I get a java.lang.ClassNotFoundException
when I use a dev transactor. am I missing something?
when using :requires
in a db function can I use my own code, or only standard libs? currently getting an error that it can’t locate the file on the classpath
ok, turns out I need to add a jar to the lib
directory of the transactor, and then I can use :requires
hey guys, wondering if there's any documentation anywhere about the full set of values that get passed to the metrics callback function when provided with -Ddatomic.metricsCallback=my.ns/handler
? This page is incomplete: http://docs.datomic.com/monitoring.html
Today I learned that d/q can return d/entity
s:
(d/q '[:find [?ent ...] :in $db :where [$db ?e :bar _] [(datomic.api/entity $db ?e) ?ent]] db)
How did I not know this?
we should do an advent calendar of cool things you can do with d/q
a bit late now I guess 🙂
@kwladyka sounds like there is a dep conflict between versions of jetty in ring and in datomic client. can you resolve it with exclusions?
@geoffk the metric callback return value is described here: http://docs.datomic.com/monitoring.html#callback-argument-format
it can contain any/all of the keys listed in this table: http://docs.datomic.com/monitoring.html#sec-5
thank you @marshall i've just found that the metrics that are actually received by the callback handler, if I enumerate through all the keys in that map include some keys that aren't documented on either of those pages - There are a bunch of Peer* metrics in the map for example when specifying the callback from a peer
@geoffk Which specific metrics are showing up? That table specifically includes the transactor metrics.
that makes sense then - is there somewhere in the docs that enumerates peer metrics ? I'm specifically trying to get peer metrics logged to CloudWatch via this handler and some custom code - a good example of a key that doesn't seem to be documented anywhere is PeerFulltextBatch
Right. No, there is not currently a list of peer-specific metrics in the docs; I can log a request to provide one