HSBeat

Beats for Java HotSpot VM. This beat ships all performance counters in HotSpot VM.

Features

• HSBeat collects periodically all raw performance counter values in Java HotSpot VM.
  • Constant values are shipped only once (first time) to Elasticsearch.
  • Monotonic and Variable values are shipped in all collection time.
• If you want to calculate these values (e.g. ratio, time), you have to implement it in your client apps.
  • HSBeat Kibana dashboard sample use dynamic scripting on Elasticsearch.
• Collects values for multiple Java processes or for a given PID
  • When a PID is not given, it collects counter values from all running Java processes that create a hsperfdata file under <tmp>/hsperfdata_*

Getting started

Collecting counters from a single Java process

$ go get github.com/YaSuenag/hsbeat
$ hsbeat -E hsbeat.modules.0.pid=<PID>

Collecting counters from all running Java processes

$ go get github.com/YaSuenag/hsbeat
$ hsbeat

Note: only process for which the user running hsbeat has read access to <tmp>/hsperfdata_*/<pid> are monitored

If you want to use sample dashboard, you can import as below:

$ import_dashboards --dir $GOPATH/src/github.com/YaSuenag/hsbeat/etc/kibana

import_dashboards is provided by Beats binary. Please see reference manual if you want to know more details.

• If you want to use sample dashboard, you have to enable scripting on $ES_HOME/config/elasticsearch.yml as below:

script.engine.groovy.inline: true