This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-01
Channels
- # aleph (2)
- # aws (23)
- # bangalore-clj (1)
- # beginners (99)
- # bristol-clojurians (1)
- # cider (3)
- # circleci (1)
- # clj-kondo (8)
- # cljdoc (4)
- # clojars (1)
- # clojure (47)
- # clojure-india (1)
- # clojure-nl (2)
- # clojure-serbia (3)
- # clojure-spec (2)
- # clojure-uk (17)
- # clojuredesign-podcast (1)
- # clojurescript (20)
- # datascript (1)
- # datomic (1)
- # emacs (1)
- # fulcro (4)
- # pathom (18)
- # ring-swagger (2)
- # shadow-cljs (31)
- # spacemacs (3)
- # tools-deps (10)
- # vscode (1)
Does anyone have any good recommendations for monitoring gc, how stressed the jvm is, potential early warning signs. I'm exposing a lot of metrics via prometheus and jmx.
is that what you mean? Or are you looking for alerting thresholds and which metrics to observe?
Using grafana + prometheus, just charting some metrics now, looks like my JVM is taking about 0.1ms to do a GC (using G1)
Other candidate options:
- datadog + their jmxagent
- jvisualvm
(free) can at times be a little awkward to connect to remote vm’s; but it’s possible… via an ssh tunnel/jmx combo etc.
- jstat -gccause <PID> 1000 > /tmp/gclog.txt
Having a gclog is a great idea, I think it can do truncation, or rollover and delete past entries. Probably.
@dharrigan Censum from jClarity is a nice tool for this, but it's commercial with 7 day trial. Oddly enough, it was one of the founders of this company that convinced me to start looking at clojure 🙂
I know the feeling re: keeping budgets tight. Might be some value in playing with the trial to see if you can get any quick insights.
yourkit is still a thing