Open topic with navigation
System settings take effect globally throughout Analytics, for example, you can set time periods when you want Analytics to stop collecting data. Email and text settings are also configured in the System settings because all the alarms in Analytics use the same email and SMS accounts to send notifications when an alarm is triggered.
The System settings are grouped on the following tabs:
Global Settings: Set up options to define time periods when you want Analytics to stop collecting data, whether or not to accept invalid SSL certificates, and whether or not to enforce Do-Not-Track privacy settings in browsers. You also need to provide an external link to Analytics so that it is possible to link to Analytics from an email or SMS notification.
Alarm Recipients: Add the contact information of those people you want to receive alerts when resources or systems trigger alerts in Analytics.
Email Settings: Enter data to enable Analytics to send emails messages when an alarm triggers. You enter the SMTP server settings including optional security configuration, as well as the email address and name notifications are sent from
SMS Settings: Enter the Twilio account data that Analytics needs to send automatic text messages when an alarm triggers. You enter the Twilio account SID, token, and Twilio phone number that Analytics uses to send the text messages.
Purge Data: Purge data collected by Analytics that is more than two months old in order to free up space on your server. You select a month and then delete all the data that precedes and includes that month's data.
User Data: Manage user data that Analytics has collected if you need to provide user information upon request or purge any identifying information in order to comply with Do-Not-Track privacy regulations.
When you set Global System settings, they affect all the resources that Analytics monitors, for example, you
Global settings can be found in Configuration | System | Global Settings tab.
You set up any of the following:
Disable Collection: An optional setting that applies to all data collection. Click the checkbox to activate the settings. Add a Start and End time during which Analytics will stop collecting data. The setting includes the start and end time you set.
To add other time period during which you want to stop collection, click Add, and then define the time period.
Accept Invalid SSL Certificate: An optional setting to allow you to monitor a website that has a self-signed certificate, an invalid host name, or a certificate that has expired.
When activated, this setting also affects ArcGIS Sever, Portal for ArcGIS, and ArcGIS Online.
Selecting this option is considered unsafe. Do not select the option unless you are certain.
Enforce Do-Not-Track Privacy Settings: An optional setting that is on by default. When you enable this setting, Analytics respects a user's Do-Not-Track browser settings. If a user has enabled Do-Not-Track in their browser and the Enforce Do-Not-Track Privacy Settings option is enabled in Analytics, no identifying information about that user is collected. Analytics continues to track their activities for statistical purposes but as an anonymous user with no association to the collected data.
Alarm recipients can be added in Configuration | System | Alarm Recipients tab.
You add the names, email addresses, and phone numbers of the people you want to receive notifications from Analytics. You can select whether the recipient receives all notification about all the Resources monitored by Analytics. Alternatively, once you have created a list of recipients, under each monitored resource, you can select particular recipients to receive alarms from specific resources.
To add an Alarm Recipient:
In Configuration, under System | Alarm Recipients tab, click Add New Recipient.
In the Add New Recipient window:
Name: Type the name of the recipient as you want it to appear in the notification email.
Email: Type in the recipient's email address (optional).
Phone Number: Type in the phone number to send SMS alerts (optional).
For Analytics to send email notifications, you need to set up an email client that Analytics can use to send emails automatically to the list of alarm recipients that you configure.
Add an Email host in Configuration | System | Email Settings tab.
You can define the following Email Settings:
SMTP Server: Enter the name of your email service, for example,
Port: Enter the port number your organization uses for email. You must specify a port.
TLS Required: If your email server uses TLS security measures, select this checkbox.
SSL is not supported.
From Address: Enter the email address that will appear in the From field of the email. You must have a From address.
From Name: Enter name to appear in the email as the sender of the email.
Authentication Type: Select one of the following types of authentication:
None: Use this option if the email server is not secured.
Basic: Use this option if the email server uses a simple username and password for security.
Windows Authentication: Use this option if the email server uses Windows Authentication, and then enter the Username, Password and the Domain of the user.
If you wish to receive a text message when an alarm triggers in Analytics, then you need to create a Twilio account for Analytics to use to automatically send SMS messages when an alarm triggers. All text messages to alarm recipients are then routed through the same Twilio account.
Add an Twilio account host in Configuration | System | SMS Settings tab.
You can define the following SMS Settings:
Twilio Account SID: The SID number you receive when you create a Twilio account. You must enter a valid SID number.
Twilio Token: The token you receive when you create a Twilio account. You must enter a valid token.
Twilio Phone Number: The Twilio phone number that the text is sent from. You must enter a valid Twilio phone number.
You can purge older data to free up space on your server.
You can only purge data that is older than two months. When you select a month, all the data prior to that month and during that month is purged.
To purge Data:
Under Configuration, in the sidebar, click System.
Select the Purge Data tab.
From the Purge All Data Collected Prior To and During drop-down list, select a month.
Beside each month, the brackets indicate the estimated space that you will free by purging that data.
Analytics tracks and collects information about how users interact with the resources that it monitors, for example, Geocortex and Esri applications. The objective of tracking user data is to establish usage patterns that can inform decisions about how to improve users' experience.
Privacy regulations in some regions indicate that if you collect user data, you must be able to retrieve and delete that data on request.
On the User Data tab in Configuration, you can search for a user's collected data by their full or partial user name or IP address. You can export the data if required, or purge the data to strip it of any identifying information. Analytics keeps the purged user data and uses the retained information for statistics about the user's activities in various applications but the data is anonymous.
To find and purge user data:
Under Configuration, in the sidebar, click System.
Select the User Data tab.
In the Search by Name or IP Address box, type in a full or partial user name or IP address.
If you type in a partial name or address, all matching users or addresses will be listed.
If the user was authenticated on sign-in to an application or resource that is monitored by Analytics, their user name and ID are listed in the results. If the user did not sign in, only their IP address is listed.