This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-22
Channels
- # admin-announcements (1)
- # aws-lambda (1)
- # beginners (38)
- # boot (48)
- # cider (11)
- # clara (4)
- # cljs-dev (61)
- # cljsrn (9)
- # clojure (68)
- # clojure-austin (3)
- # clojure-greece (9)
- # clojure-mexico (6)
- # clojure-russia (40)
- # clojure-spec (165)
- # clojure-uk (134)
- # clojurescript (37)
- # cursive (5)
- # datomic (25)
- # defnpodcast (2)
- # hoplon (1)
- # jobs (1)
- # juxt (1)
- # lein-figwheel (3)
- # leiningen (4)
- # mount (14)
- # off-topic (8)
- # om (29)
- # onyx (9)
- # protorepl (4)
- # quil (1)
- # re-frame (56)
- # reagent (3)
- # rethinkdb (1)
- # spacemacs (4)
- # specter (12)
- # test-check (2)
- # testing (1)
- # vim (12)
- # yada (4)
Any suggestions on best practices for monitoring/metrics for onyx? I have setup riemann/influx/grafana and have proven I can manually connect to riemann and get events into influx. What are some key values that we should look out the keys onyx can send events for ?
Is the monitoring config still the 3 param in the start-peer call? It looks like this is the env-config?
@camechis: See the monitoring section of the docs. http://www.onyxplatform.org/docs/user-guide/latest/monitoring.html
@michaeldrogalis: Yeah, I am looking at that. Wasn’t sure what all the metrics are and whats the most useful
Also it says to pass the config in as the third param into the start-peer but that looks to be the env-config
@camechis: That's an error in the docs, we moved it a couple of versions ago.
We help with monitoring/metrics and tuning under commercial contracts. There's too much to explain in chat. The cheat sheet names most of the critical values emitted from monitoring.