Release Content
| The software components of Elasticsearch stack are no longer part of the delivery. Please download them from elastic.co or get it from your package manager. |
Overview
-
license
-
sbom
-
resources
-
analytics
-
elasticsearch
-
bin
-
dev-console
-
elasticsearch
-
examples
-
filebeat
-
ingest
-
kibana
-
logstash
-
-
experience-builder
-
python
-
monitor_setup
-
pipelines
-
-
webapp-integration
-
-
sql
-
tomcat-jndi-resources
-
tools
-
-
monitor.war
-
monitor-analytics.war
-
ct-monitor-analytics-js-[VERSION].jar
-
INFO.txt
-
README.txt
-
vulnerability-report.md
Details
monitor.war/monitor-analytics.war-
The two web applications are deployed in a Tomcat and are used to set up monitoring services and collect user interaction data in map.apps.
ct-monitor-analytics-js-[VERSION].jar-
The jar file contains the bundles that integrate with map.apps to capture user interactions.
resources/analytics/elasticsearch-
This folder contains necessary configuration files for configuring and operating the elasticsearch stack. This comprises:
bin-
scripts to explain environment variables being read by logstash
dev console-
Elasticsearch index template policy configuration to be used in Kibana
Dev Tools logstash-
Logstash data pipelines for Analytics
kibana-
Kibana dashboards, queries and widgets
filebeat-
Filebeat configuration (ArcGIS)
ingest-
Elastic ingest pipelines
resources/analytics/experience-builder-
Integration widget with ArcGIS Experience Builder
resources/analytics/python-
The
pythonfolder contains files to use service.monitor in a scripted way. This comprises means to setting up the Elasticsearch related parts of service.monitor and scripts to pipeline Safe FME Flow data to Elastic. resources/analytics/webapp-integration-
The
webapp-integrationfolder contains files that allow integration with the con terra products map.apps and security.manager EE.