Open topic with navigation
The following issues were fixed:
Attempting to remove a website from Configuration would cause an error.
Resource Alarms on the Summary tab looked identical if the resource name was the same – even when they came from different locations.
The default sort-order for table content panels was not optimal.
The Windows Event Logs Trends panel for the Hub server incorrectly showed Events from remotely-monitored servers.
The Session Info panel did not show a chart for the Geocortex App User.
The alarm panels in Trends were not loading map services that had fired alarms or that had been stopped.
It was not possible to configure and add email settings after uninstall/reinstall.
The ArcGIS Server Active Alarm Count incorrectly included Alarms for Stopped or Deleted Services.
Resources with similar URLs prevented migration from completing successfully.
The Maximum Concurrent User count for applications was inconsistent when drilling in to the hourly view.
The Web Application Status tab showed an error after Web App Builder applications were configured.
When switching from Remote Monitoring to an Agent, some Resources were duplicated.
When switching from Agent to Remote Monitoring, there were issues with Servers and ArcGIS Servers and likely other resources.
When the Collection Failure alarm was triggered, it caused resources to enter a "Child has Critical Error" state.
The Web App relay was unable to send a token-with-service URL.
Sidebar: The Alarm panel kept loading when you toggled the Deselect All button in Geocortex Essentials and Geocortex Applications.
When an ArcGIS server was down, a misleading Last Value appeared for the ArcGIS Server Request Failure alarm.
The Average Session Duration panel and IP Addresses panel in Trends: Web Application contained no data.
Version 1.5 of Analytics is focused on giving you fine-grained control of alarms and alarm notifications but other notable changes include improved data collection, new content panels and improvements to the Summary tab.
You can now use the Alarm Recipients tab in Configuration | System to add the recipients you want to receive alarm notifications by either Email or SMS. You can configure a recipient to receive all Resource alarms in the Update Recipient dialog when you add them as an Alarm Recipient or go to a resource and configure them to receive notifications about those specific alarms.
Alarms Configuration Cards
Alarms for each resource are displayed on cards that make it easy to see the status of each alarm, who the recipients are for notifications on each alarm and how often the alarm has triggered. The link to configure each alarm is right on the card , so it is easy to configure the exact alarm you want for the correct resource.
When you configure an alarm, you now have the option to select a batch script (.bat) to run when that alarm is triggered. In order to see scripts listed in the alarm window for selection, they must be in the Scripts folder on the Analytics Hub server. The default installed Scripts folder is:
Alarm UI and Process Improvements
The cards on the Summary page now represent active Alarms that may need attention. The top chart on the Summary page gives a visual overview of the frequency of Alarms over the past 48 hours.
You can now view process usage (memory consumption and CPU usage) in Trends for ArcGIS Servers and Portals. The ArcGIS Server panel also includes process usage for individual services on your ArcGIS Server.
If data collection fails because credentials expire or permissions are changed, the UI shows an indicator in Status and Trends with details about why the failure occurred.
The following issues were fixed:
Version 1.4 of Geocortex Analytics involved a complete rewrite of all the probes and replacement of the collectors with other methods of gathering data. Version 1.4 also included many improvements to reliability, stability and performance, for example, a reduction in the strain of monitored resources like ArcGIS Server. Other improvements involved key features like clustering, individual user information, and alarms on secured Essentials sites.
All the probes in Analytics 1.4.x have been rebuilt and redesigned to increase reliability, performance, and reduce the strain on monitored resources like ArcGIS Server. All the collectors have been replaced with other methods of acquiring data. The new monitoring method intelligently detects when to probe active or dormant services in order to minimize the impact to ArcGIS Server performance.
The rebuild made some reports like System Collector Downtime and Collector Status redundant as the new probing and collection methods use a centralized system.
Analytics now uses intelligent probing when monitoring ArcGIS Servers. To monitor services intelligently, Analytics needs additional administrator access credentials so that it can determine whether services are active or inactive at any given time. Previously, providing administrator credentials was optional.
The additional credentials make it possible for Analytics to determine how busy an ArcGIS Server is and to adapt the timing of its monitoring to ensure its own activity does not add to the strain of a busy resource. For example, Analytics will only probe a few services every hour on a very busy resource but it ensures that all the services are probed over a 24 hour period.
Configured collection intervals can be affected by the new probing method. If Analytics is scheduled to probe a service and it is already active, Analytics respects its collection interval. If a service is inactive, Analytics only probes within 24 hours.
When you set up an ArcGIS Server, you can now specify multiple log directories to monitor on different remote servers. If the server is in a different time zone than the Analytics Hub server, you can specify the time zone that the new server is in.
Updates to Portals included the removal of Web Map availability alarms as web maps cannot be unavailable unless ArcGIS Online or Portal for ArcGIS is unavailable. We retained the alarm for Portal for ArcGIS availability, and with ArcGIS Online’s 99.9% uptime service level agreement, we determined that web map alarms were an unnecessary strain on monitoring.
The ability to configure Analytics by changing the xml code in the
role.config files no longer exists. All configuration is now done through the Analytics interface under Configuration. During the upgrade to Analytics 1.4, any custom configuration was transferred to the new database so that it could be seen and edited in the Configuration interface.
role.configfiles, was the Enabled setting for premium Esri services. This setting was disabled during the upgrade and must be manually enabled again in Configuration after the upgrade. The purpose of disabling this setting was to ensure that Analytics did not collect on premium services without users being aware of it, as that can cost credits.
Improvements to Analytics 1.4 mean that it is no longer necessary to cluster Geocortex Analytics with Geocortex Essentials if you want Analytics to monitor Geocortex Essentials. This change means that it is now easier to set up Analytics for new customers. It also enables existing customers to monitor more than one Essentials across environments, for example, across both QA and production deployments using a single Analytics instance without any concerns about the shared Elasticsearch resources for Essentials.
If your current deployment of Analytics includes clustering with Geocortex Essentials, when you upgrade to Analytics 1.4.x, you must un-cluster from Essentials to continue monitoring. To help with unclustering, Analytics 1.4.x ships with an Unclustering Utility that does the unclustering for you. You need to run the Unclustering Utility on the Hub server, all Agent servers, and any servers that have Essentials installed on them. For more information,
New panels that show information about how individual users are using your applications make it possible to monitor, in detail, how users are interacting with your applications. The new information gives you greater visibility into your end users’ experience.
The new Individual user reports include:
You can access individual user reports by clicking a user in the Users panel within a Geocortex or Web Application in the Analytics interface.
The collection and presentation of more information on individual users made it important to also provide the ability to opt out of displaying this information for privacy reasons. Adding Do-Not-Track privacy compliance to Analytics also became necessary because of changing global legislation to protect individual's privacy.
To provide comprehensive compliance for all the regions of the world, Analytics 1.4 was built to include privacy compliance based on the most rigorous current privacy legislation, which is the European Unions’ General Data Protection Regulation, that came into effect on May 25, 2018. For more information, see Privacy Regulations and Analytics
To enforce privacy compliance, Analytics uses the browser privacy setting to determine if each user has consented to being tracked or not.
We also provide the ability for Analytics administrators to retrieve or delete a user’s personal data (user name and IP address) if requested. Deletion of a user's personal data retains what the user did within the GIS system but marks their data as anonymous.
It remains your (the customer's) responsibility to comply with the privacy laws that apply in your region, whether it is the European Union, California or elsewhere. Our guide includes a reference to possible tracking consent text you could use but it is your responsibility to apply it based on your organization's privacy rules. If you serve a region where do-not-track is not required, we have provided the option to disable do-not-track enforcement in Analytics configuration settings.
There is in-app help for each content panel to supply information about the contents and usability of each panel. The in-app help aims to communicate what the panel is for and how you can use the information.