Monitoring events
Overview
![monitoring](../../../_images/installation/analytics/datasources/monitoring.png)
Details about service.monitor Monitoring executed monitoring executions can be stored in the local database. Alternatively they can also be
-
sent to Analytics' Logstash pipeline via GELF protocol or
-
directly to elastisearch via http (recommended)
Procedure
-
Configuration of the /monitor web application
Configuration of the /monitor web application (directly to Elasticsearch)
Add the following changes to the application.properties
file of service.monitor Monitoring:
Send events to Elastic using http
#### Storing monitored events directly in elasticsearch ####
event.storage.elastic.http.enabled=true
event.storage.elastic.index.name=ct-monitoring
event.storage.elastic.buffer.size=5
monitoring.elastic.url=http://localhost:9200
monitoring.elastic.username=elastic
monitoring.elastic.password=<password>
The above configuration assumes that the Elastic process is running on the same machine as the Tomcat.
Configuration of the /monitor web application (via Logstash pipeline)
Add the following changes to the application.properties
file of service.monitor Monitoring:
Send events via Logstash to Elastic
#### Storing monitored events in elasticsearch via a logstash pipeline ####
# This is very useful if you want to leverage kibana widgets and dashboards
event.storage.elastic.enabled=true
event.storage.elastic.logstash.host=localhost
event.storage.elastic.logstash.port=12203
The above configuration assumes that the Logstash process is running on the same machine as the Tomcat.