ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-03-17 17:45:17 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

[ENT-1711] Update node monitoring docs. (#1218)

Browse Source 
* [ENT-1711] Update node monitoring docs.

* [ENT-1711] Update node monitoring docs.

* [ENT-1711] Update node monitoring docs.

* [ENT-1711] Update node monitoring docs.

* Update node monitoring docs.

* Update node monitoring docs.
This commit is contained in:
Florian Friemel 2018-07-10 14:28:02 +01:00 committed by GitHub
parent f4972f922a
commit e887d220bb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/source/node-administration.rst
View File

@ -65,7 +65,7 @@ database should be via the usual database tools mechanisms, including access con
Monitoring your node
--------------------
There are two ways to monitor performance and health of a node in Corda Enterprise:
This section covers monitoring performance and health of a node in Corda Enterprise with Jolokia and Graphite. General best practices for monitoring (e.g. setting up TCP checks for the ports the node communicates on, database health checks etc.) are not covered here but should be followed.
Monitoring via Jolokia
@ -96,8 +96,11 @@ Here are a few ways to build dashboards and extract monitoring data for a node:
It can bridge any data input to any output using their plugin system, for example, Telegraf can
be configured to collect data from Jolokia and write to DataDog web api.
The Node configuration parameter `jmxMonitoringHttpPort` has to be present in order to ensure a Jolokia agent is instrumented with
the JVM run-time.
In order to ensure that a Jolokia agent is instrumented with the JVM run-time, you can choose one of these options:
* Specify the Node configuration parameter `jmxMonitoringHttpPort`.
* When using the launcher, add the line `-javaagent:../../drivers/jolokia-jvm-1.6.0-agent.jar=port=7777,host=localhost` to the `[JVMOptions] sections of the `launcher/app/launcher.cfg`. Make sure to place the Jolokia agent that you specify there into the `drivers` folder.
* Start the node with `java -jar corda.jar -javaagent:drivers/jolokia-jvm-1.6.0-agent.jar=port=7777,host=localhost`.
The following JMX statistics are exported: