4.5
Analytics (4.5.3)
Analytics (4.5.0)
Story
|
Provide Dashboard with real time FME job execution information |
|
Provide visual information to understand FME engine occupation by job execution |
|
Harvest FME Server job execution log lines |
|
Initial FME Integration Dashboard |
|
Provide Elastic Index Lifecycle Management for "ct-log" data |
|
Provide Elastic Index Lifecycle Management for all logstash pipelines |
|
Provide means to analyze histogram data aggregated by "hour of day" or "day of week" |
Bug & Improvement
|
Verify arcgis logstash pipeline is capable of loading and transforming arcgis data store |
|
Collect app title additionally to app id |
|
Pseudonomize ArcGIS user name by default in logstash pipeline |
|
Pseudonomize service.monitor Monitoring user name by default in logstash pipeline |
|
Track registered bundles on application framework events |
|
Improve FME Server job & log line integration |
Monitoring (4.5.1)
Bug & Improvement
|
Clarify ssl smtp server usage |
|
Bean reference not found in ONLY_AUTHN mode |
|
data.directoy.location gets replaced during new rollout creation |
|
Verify incoming monitoring template string to be valid JSON |
|
Support Credential-Templates-Usage when applying DynamicRequests on job creation page |
|
Provide reason information if an expectation fails |
|
Allow FME Job Schedule monitoring on FME schedules not running with a CRON schedule |
|
Show next execution time in dashboard for active services |
|
Simplify navigation to notification & monitoring templates and expectations when editing jobs |