Processes¶
The following processes and subprocesses can be monitored with "insight-status"
- Wildfly or tomEE
- Gateway
- Indexer
- Reldb
- Elastic
- Kibana
Maximo¶
Its recommended to monitor Maximo and Apache httpd additionally.
Requirements¶
insight-status.bat The following scripts are used for monitoring:
- insight-status.bat
- insight-status-servcice.bat
- insight-status.sh
- loop.sh
Insight-status Script¶
Insight-status executes http-calls for every component (wildfly, elasticsearch, kibana, indexer) and writes a state-document to elasticsearch. It also prints the states to console.
Please adjust path to jre in insight-status.
Loop Script¶
Loop is calling insight-status.sh periodically with 5 sec wait-time on Linux.
In insight-status.bat the loop is directly implemented.
Insight-status¶
The script insight\monitoring\insight-status-service.bat for Windows can be used to start insight-status.bat as a service
-
To install the service please call:
insight-status-service.bat install -
To remove the service please call:
insight-status-service.bat remove
The following command can be used to run insight-status periodically in background without output:
nohup ./loop.sh >/dev/null 2>&1 &
Monitoring-Dashboard.json¶
Monitoring-Dashboard.json defines a Kibana-Dashboard to visualize the state-documents written by insight-status.sh.
The following requirements must be met:
- Insight-indexer is successfully deployed
- Insight-status.bat as a service on Windows or loop.sh on linux is running
- Elastic and Kibana are running
The dashboard can be activated by the following steps:
- Open Kibana-client (localhost/insight/kibana)
- In "Settings" -> "Indices" -> "Configure an index pattern" define index pattern "insight-monitoring" with timebased events
- In "Settings" -> "Obects" -> "import" you can import the Monitoring-Dashboard.json
Start Kibana-Client and open dashboard "monitor". You will get a view like this:
