Data sources

If Analytics is activated in map.apps and security.manager, concrete user interactions of the users are recorded and sent to Elasticsearch via (the monitor-analytics webapp) and a Logstash pipeline. The collected data can then be viewed and analyzed using the dashboards available in map.apps Manager. Since version 4.4, this data can also be analysed in a similar way using the Kibana Dashboards.

In recent years, central log data aggregators have become very important for the successful operation of IT systems and this is one of the core competencies of the Elasticsearch Stack. The products and software artifacts developed at con terra increasingly support the storage of application log files in such central systems instead of writing this information to the local file system. service.monitor Analytics contains a logstash pipeline that can record and modify log events and send them to Elasticsearch for storage.

service.monitor Monitoring and Analytics can be linked together via a simple data transfer. If the transfer is active, all information about individual monitoring events (service, job, URL, success, error, etc.) is sent from the monitoring to a Logstash pipeline, where it is modified and sent to Elasticsearch for storage. This data can then be meaningfully analyzed using the convenient interaction options of the dashboards.

service.monitor does also support collecting ArcGIS Server and Portal for ArcGIS logfiles. It does additionally provide simple methods for visualization and analyzation of data.

service.monitor also allows the display of Safe FME job information and log output that has arisen during the execution of jobs. By regularly querying the FME job repository, detailed data on the use and utilisation of the FME infrastructure is available, which can be displayed statistically and visually on the dashboards.